Post or Throttled Graphics Options

[jamesmarkchan]

This feature is for lower processing system specs or evaluating the impact of graphics rendering during the benchmark.

This adds a mode where the user can select to not update the graphics in realtime and instead update after the benchmark is completed.

Throttled option is to provide menu options to select this mode and input when the graphics are updated like after n samples or after an update window like 500ms. (maybe just give them options for 100ms, 500ms, 1s)

Should be able to introduce both options for the user.

Perhaps introduce a submenu called Render Mode somewhere in the options menu with child entries:

• Per Sample (our current mode)
• Per Operation (like after a read operation and a write operation)
• Per 1000 (ms)
• Per 500 (ms)
• Per 100 (ms)

Definitely worth saving the render mode selection as part of the benchmark meta data to persist.

[jamesmarkchan]

@vpstackhub i hope you are having an incredible labor day weekend. when you are ready to jump back into the fray i though this item might be worth your consideration.

[vpstackhub]

I’d like to take on this feature next.
I’ll implement a Render Mode submenu under the Options menu, with the following user-selectable modes:

Per Sample (current behavior)

Per Operation (after each read/write)

Throttled (100 ms, 500 ms, 1000 ms options)

I’ll start by updating the UI, then adjust the chart update logic accordingly, and ensure the user’s choice is persisted. Let me know if you'd prefer this grouped differently or want any additional modes.

[jamesmarkchan]

sounds good @vpstackhub, good to practice w the code, if you could hold of on commits for a moment, i'm about to push a refactor that will touch a number of files. ideally if you get the changes identified and well documented can put them ontop of mine.

here are the files that i'm modifying atm:

I know to do this feature you will have to work in MainFrame.java and BenchmarkWorker.java as well.

[vpstackhub]

Thanks, James sounds good. I’ll hold off on any commits for now and just continue testing locally. I’ll keep track of the changes I’m making so I can reapply them cleanly once your refactor is in. Appreciate the heads-up!Valerio. On Sep 14, 2025, at 3:14 PM, James Mark Chan ***@***.***> wrote:jamesmarkchan left a comment (JDiskMark/jdm-java#78) sounds good @vpstackhub, good to practice w the code, if you could hold of on commits for a moment, i'm about to push a refactor that will touch a number of files. ideally if you get the changes identified and well documented can put them ontop of mine. here are the files that i'm modifying atm: image.png (view on web) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>