Project

General

Profile

Feature #18923

Printout option of Memory Tracker service

Added by Liang Li over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
02/08/2018
Due date:
% Done:

0%

Estimated time:
Scope:
Internal
Experiment:
g-2
SSI Package:
art
Duration:

Description

The output of memory tracker service has recently changed from a direct printing on screen to saving everything into a SQL database file. This has made the debugging process more difficult and more time consuming. If there is a switch or option to revert this change to use the previous printing output instead (the default output can be still the SQL database), it would be nice to have, thanks!

History

#1 Updated by Kyle Knoepfel over 2 years ago

  • Status changed from New to Feedback

The per-module information for the MemoryTracker is no longer printed at the end of the job due to issues with maintainability. In order to get the information, you should use the sqlite3 scripts that are installed with your version of art. Keep in mind that the column width may truncate what you see on the screen.

We are happy to assist you in figuring out how to use the SQLite scripts.

# Check which SQLite scripts are available (make sure you have art set up first)

$ ls -1 $ART_DIR/tools/sqlite/memoryTracker
max-delta-rss-events.sql
max-delta-rss-modules.sql
max-delta-vsize-events.sql
max-delta-vsize-modules.sql
max-rss-events.sql
max-rss-modules.sql
max-vsize-events.sql
max-vsize-modules.sql
peak-summary.sql

# Now take your db, and choose one of the scripts (e.g.) “max-delta-rss-modules.sql”:

$ sqlite3 -header -column my-own-memoryTracker.db < $ART_DIR/tools/sqlite/memoryTracker/max-delta-rss-modules.sql
Path        ModuleLabel     ModuleType             DeltaRSS (MB)  Run         SubRun      Event
----------  --------------  ---------------------  -------------  ----------  ----------  ----------
p1          TriggerResults  TriggerResultInserter  1.081344       1           0           1
p1          TriggerResults  TriggerResultInserter  0.81100800000  1           0           3
p1          TriggerResults  TriggerResultInserter  0.54067200000  1           0           2
p1          a1              TestSimpleMemoryCheck  0.54067200000  1           0           6
p1          a1              TestSimpleMemoryCheck  0.54067200000  1           0           7
p1          a1              TestSimpleMemoryCheck  0.54067200000  1           0           8
p1          a1              TestSimpleMemoryCheck  0.54067200000  1           0           9
p1          a1              TestSimpleMemoryCheck  0.54067200000  1           0           10
p1          a2              TestSimpleMemoryCheck  0.54067200000  1           0           1
p1          a2              TestSimpleMemoryCheck  0.54067200000  1           0           4
p1          a2              TestSimpleMemoryCheck  0.54067200000  1           0           7
p1          a2              TestSimpleMemoryCheck  0.54067200000  1           0           8
p1          a2              TestSimpleMemoryCheck  0.54067200000  1           0           10
p1          a3              TestSimpleMemoryCheck  0.54067200000  1           0           3
p1          a3              TestSimpleMemoryCheck  0.54067200000  1           0           4
p1          a3              TestSimpleMemoryCheck  0.54067200000  1           0           10

#2 Updated by Kyle Knoepfel about 2 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF