Skip to content

update DCClsComboEngine.java to set limit for cluster combos in case of memory explosion - #1352

Merged
baltzell merged 4 commits into
developmentfrom
iss1336
Jul 30, 2026
Merged

update DCClsComboEngine.java to set limit for cluster combos in case of memory explosion#1352
baltzell merged 4 commits into
developmentfrom
iss1336

Conversation

@tongtongcao

@tongtongcao tongtongcao commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Response to #1336, set limit for DC cluster combos.
By default, limit is 1M for each sector. If combos reach the limit for a sector, then the first 1M combos will be kept.
Totally, the memory usage is estimate to be ~1.8G at most, if all 6 sectors reach the default limit.
Limit of 1M is supposed to be large enough. The plot show distribution for # of combos of a sector using run 6666 for test.
Plot_07-16-2026_09 43 03_AM

@baltzell

Copy link
Copy Markdown
Collaborator

Isn't 1e6 very conservative? Your data stops at 8e4?

@baltzell

Copy link
Copy Markdown
Collaborator

And what's the max memory needed for 1e6?

@tongtongcao

Copy link
Copy Markdown
Collaborator Author

The test is after denoising, and run 6666 is 50nA. Consider much higher luminosity for the future and potential reconstruction without denoising, I set much higher value for limit.
I think that 1.8G memory requirement at most is acceptable.
What's your suggestion?

@tongtongcao

Copy link
Copy Markdown
Collaborator Author

Reset default limit of cluster combos for a sector from 1M to 100k.

@baltzell
baltzell enabled auto-merge (squash) July 30, 2026 19:48
@baltzell
baltzell merged commit e89c0e2 into development Jul 30, 2026
22 checks passed
@c-dilks
c-dilks deleted the iss1336 branch July 31, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants