feat: implement 20 FPS render target with dirty checking optimization #320

Merged

freemo merged 3 commits from feature/m2-render-fps into master 2026-03-16 19:54:59 +00:00

Conversation 0 Commits 3 Files changed 5 +1627

freemo commented 2026-03-16 15:25:15 +00:00

Owner

Copy link

Summary

• Implement RenderLoop class with 20 FPS target (50ms per frame)
• Frame timing with sleep compensation for consistent frame rates
• Frame overrun handling: skip sleep immediately if processing exceeds budget
• FrameStats tracking for performance monitoring

Implementation Details

• RenderLoop runs on a dedicated thread, draining RenderOp queue each frame
• Configurable FPS parameter (default 20)
• Thread-safe start/stop lifecycle with graceful shutdown
• Integration with existing DirtyCheckStage for per-window content hashing

Testing

• 32 unit test scenarios in tests/unit/render_fps.feature
• 15 integration test scenarios in tests/integration/render_fps_integration.feature
• All render-related tests pass (98 scenarios, 333 steps)

Files Changed

• lib/aethyr/core/render/frame_scheduler.rb - New RenderLoop and FrameStats classes
• tests/unit/render_fps.feature - Unit tests
• tests/unit/step_definitions/render_fps_steps.rb - Step definitions
• tests/integration/render_fps_integration.feature - Integration tests
• tests/integration/step_definitions/render_fps_integration_steps.rb - Step definitions

Closes #308

## Summary - Implement `RenderLoop` class with 20 FPS target (50ms per frame) - Frame timing with sleep compensation for consistent frame rates - Frame overrun handling: skip sleep immediately if processing exceeds budget - `FrameStats` tracking for performance monitoring ## Implementation Details - `RenderLoop` runs on a dedicated thread, draining RenderOp queue each frame - Configurable FPS parameter (default 20) - Thread-safe start/stop lifecycle with graceful shutdown - Integration with existing `DirtyCheckStage` for per-window content hashing ## Testing - 32 unit test scenarios in `tests/unit/render_fps.feature` - 15 integration test scenarios in `tests/integration/render_fps_integration.feature` - All render-related tests pass (98 scenarios, 333 steps) ## Files Changed - `lib/aethyr/core/render/frame_scheduler.rb` - New RenderLoop and FrameStats classes - `tests/unit/render_fps.feature` - Unit tests - `tests/unit/step_definitions/render_fps_steps.rb` - Step definitions - `tests/integration/render_fps_integration.feature` - Integration tests - `tests/integration/step_definitions/render_fps_integration_steps.rb` - Step definitions Closes #308

freemo force-pushed feature/m2-render-fps from ea868f6f4e to 8828a401cf 2026-03-16 16:56:56 +00:00 Compare

freemo force-pushed feature/m2-render-fps from 8828a401cf to 7af387f1a0 2026-03-16 17:31:35 +00:00 Compare

freemo force-pushed feature/m2-render-fps from 7af387f1a0 to 0d648cfabb 2026-03-16 19:54:50 +00:00 Compare

freemo merged commit 0d648cfabb into master 2026-03-16 19:54:59 +00:00

freemo deleted branch feature/m2-render-fps 2026-03-16 19:55:00 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

Blocked

Cannot proceed, depends on unresolved issue

  

Duplicate

Issue is a duplicate of an existing one

  

MoSCoW/Could Have

Desirable but not necessary, included if time permits

  

MoSCoW/Must Have

Essential, project cannot ship without it

  

MoSCoW/Should Have

Important but not strictly essential

  

Points/1

Estimated effort: 1 story points

  

Points/13

Estimated effort: 13 story points

  

Points/2

Estimated effort: 2 story points

  

Points/21

Estimated effort: 21 story points

  

Points/3

Estimated effort: 3 story points

  

Points/5

Estimated effort: 5 story points

  

Points/8

Estimated effort: 8 story points

  

Priority/Backlog

Not yet prioritized

  

Priority/Critical

Must be addressed immediately

  

Priority/High

Important, should be completed soon

  

Priority/Low

Nice to have, not time-sensitive

  

Priority/Medium

Normal priority, valid and should be addressed

  

State/Completed

Issue resolved and all PRs merged

  

State/In progress

Someone is actively working on this issue

  

State/In review

Implementation complete, PR submitted for review

  

State/Paused

Work temporarily suspended, typically blocked

  

State/Unverified

Issue created but not yet reviewed by a maintainer

  

State/Verified

Maintainer confirmed valid and actionable

  

State/Wont Do

Deliberate decision not to address this issue

  

Type/Bug

A defect in existing functionality

  

Type/Epic

Large body of work broken into multiple issues

  

Type/Feature

A new capability or user story

  

Type/Legendary

Major strategic pillar composed of multiple Epics

  

Type/Task

Technical or administrative work (not bug or feature)

  

Type/Testing

Test-only work item (TDD, test infrastructure, coverage)

No labels

Blocked

Duplicate

MoSCoW/Could Have

MoSCoW/Must Have

MoSCoW/Should Have

Points/1

Points/13

Points/2

Points/21

Points/3

Points/5

Points/8

Priority/Backlog

Priority/Critical

Priority/High

Priority/Low

Priority/Medium

State/Completed

State/In progress

State/In review

State/Paused

State/Unverified

State/Verified

State/Wont Do

Type/Bug

Type/Epic

Type/Feature

Type/Legendary

Type/Task

Type/Testing

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

aethyr/Aethyr!320

No description provided.