Skip to content

Update profile enum buffer sizing to match the number of settings, improving scan performance - #468

Merged
Orbmu2k merged 1 commit into
Orbmu2k:masterfrom
A-M-E-00:perf/profile-enum-buffer-sizing
May 31, 2026
Merged

Orbmu2k merged 1 commit into
Orbmu2k:masterfrom
A-M-E-00:perf/profile-enum-buffer-sizing

Conversation

@A-M-E-00

Copy link
Copy Markdown
Contributor
  • Profile scanning currently reads every profile through a fixed 512-slot buffer, even though most profiles only have a handful of settings. Each slot is ~12 KB, so every profile incurs a cost of moving ~6 MB to and from the driver no matter how much data it actually holds
  • Now sizes the buffer to each profile's actual setting count (retrieved through the numOfSettings property exposed from the driver), so it only moves what's needed
  • During testing, initial scanning was noticeably faster; saw ~19% reduction in scan time.

@A-M-E-00 A-M-E-00 changed the title Update profile enum buffer sizing to match the number of settings Update profile enum buffer sizing to match the number of settings, improving scan performance May 31, 2026
@Orbmu2k
Orbmu2k merged commit 4a4d1e1 into Orbmu2k:master May 31, 2026
@A-M-E-00
A-M-E-00 deleted the perf/profile-enum-buffer-sizing branch May 31, 2026 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants