Project

General

Profile

Feature #5665

Support #7559: Memory check issues for Sirius A

SimpleMemoryCheck peak memory from the O.S.

Added by Gianluca Petrillo almost 6 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Kyle Knoepfel
Category:
Infrastructure
Target version:
1.13.00
Start date:
03/15/2014
Due date:
% Done:

100%

Estimated time:
4.00 h
Spent time:
4.00 h
Scope:
Internal
Experiment:
LArSoft
SSI Package:
art
Duration:

Description

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 VmPeak in /proc/PID/status.

Related issues

Related to art - Feature #7751: Implement new sqlite-driven memory check service Closed01/30/2015

History

#1 Updated by Christopher Green almost 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.

#2 Updated by Christopher Green almost 6 years ago

  • Target version changed from 521 to 1.10.00

#3 Updated by Christopher Green over 5 years ago

  • Target version changed from 1.10.00 to 1.14.00

#4 Updated by Christopher Green over 5 years ago

  • Target version changed from 1.14.00 to 1.13.00

#5 Updated by Kyle Knoepfel about 5 years ago

  • Assignee set to Kyle Knoepfel
  • Parent task set to #7559

#6 Updated by Kyle Knoepfel about 5 years ago

  • Status changed from Accepted to Assigned

#7 Updated by Kyle Knoepfel about 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 SimpleMemoryCheck.

#8 Updated by Kyle Knoepfel almost 5 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

The new MemoryTracker service has been implemented. The VmPeak quantity is now given at the top of the general summary.

Implemented with 66bcc29c.

#9 Updated by Kyle Knoepfel almost 5 years ago

  • Related to Feature #7751: Implement new sqlite-driven memory check service added

#10 Updated by Christopher Green almost 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF