Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SplineMPE scans fail to start #60

Closed
mlincett opened this issue Aug 18, 2023 · 4 comments
Closed

SplineMPE scans fail to start #60

mlincett opened this issue Aug 18, 2023 · 4 comments
Assignees

Comments

@mlincett
Copy link

Currently, scans with SplineMPE fail to start because the server hits the 8 GB memory limit.

This also causes an inconsistency in the database since the manifest can be retrieved from the scan_id but the scan_id does not appear in the list for that particular event.

Example: 7ebf7b83913948e2bd12d52703ecace9.

@ric-evans ric-evans self-assigned this Aug 30, 2023
@ric-evans
Copy link
Member

ric-evans commented Aug 30, 2023

I'll add a REST argument to increase the server's memory request: #62

@ric-evans
Copy link
Member

The data inconsistency is consistent with #57

@ric-evans
Copy link
Member

Note that this was hitting a limit of 512MB, the client workers have a default of 8GB

@mlincett
Copy link
Author

mlincett commented Sep 1, 2023

Note that this was hitting a limit of 512MB, the client workers have a default of 8GB

Thank you. SplineMPE does not load spline tables server-side but still loads some IceTray modules to pre-process the event. It makes sense that I would use more than 512 MB but I would not expect huge consumption nevertheless.

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

No branches or pull requests

2 participants