You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NMX uses relatively large amount of raw data, so we might need to have an option to monitor/log memory consumption.
i.e. The original script from the owner was using tracemalloc to monitor memory.
It can probably be done in a similar way to the beamlime benchmarking...?
The text was updated successfully, but these errors were encountered:
I don't think we should worry about such things now. NMX experiments will run a long time with not that many events so data volume should not be a problem any more than for other instruments.
We can always process chunks in wall-time if files get too large, i.e., avoid the problem instead of adding monitoring.
NMX uses relatively large amount of raw data, so we might need to have an option to monitor/log memory consumption.
i.e. The original script from the owner was using
tracemalloc
to monitor memory.It can probably be done in a similar way to the
beamlime
benchmarking...?The text was updated successfully, but these errors were encountered: