Support #7559: Memory check issues for Sirius A
SimpleMemoryCheck peak memory from the O.S.
I notice that the "peak" memory as reported by
SimpleMemoryCheck always matches one of the memory report entries.
Linux provides another estimation of the real peak memory (possibly a better one).
This figure is important in environments with limited resources and can differ sensibly from the reported peak.
That number can be found as
#1 Updated by Christopher Green over 6 years ago
- Category set to Infrastructure
- Status changed from New to Accepted
- Target version set to 521
- Estimated time set to 4.00 h
- Experiment LArSoft added
- Experiment deleted (
- SSI Package art added
- SSI Package deleted (
I think we can add this as an additional piece of information rather than by changing the way we calculate this particular number. That way we can actually see any discrepancies between the two metrics.
#7 Updated by Kyle Knoepfel over 5 years ago
We have addressed a number of issues related to
SimpleMemoryCheck, as implemented with commit
fbc282dd. We are also developing a new memory service called
MemoryTracker that will be
sqlite3-driven, just as the new
TimeTracker service is. Since
VmPeak is a feature to be added to the service, we will include it in
MemoryTracker and refrain from adding additional data to