Skip to content

Print Memory Peak Working Set Usage#168

Merged
ryanlai2 merged 5 commits intomasterfrom
user/kiyoung/peak-working-set
Feb 21, 2019
Merged

Print Memory Peak Working Set Usage#168
ryanlai2 merged 5 commits intomasterfrom
user/kiyoung/peak-working-set

Conversation

@yskim1501
Copy link
Copy Markdown
Contributor

This is to print out peak working set of a process.

Examples of memory perf output with this change

-perf all

Working Set Memory usage (load): 564.152 MB
Working Set Memory usage (session creation): 1061.62 MB
Working Set Memory usage (bind): 0.410156 MB
Working Set Memory usage (evaluate): 1.61719 MB
Peak Working Set Memory Difference (from start to load): 563.926 MB
Peak Working Set Memory Difference (from model load to session creation): 1609.46 MB
Peak Working Set Memory Difference (from session to bind): 0 MB
Peak Working Set Memory Difference (from bind to evaluate): 0 MB
Working Set Memory usage (load, bind, session creation, and evaluate): 1627.8 MB
Peak Working Set Memory Difference (load, bind, session creation, and evaluate): 2173.39 MB

**-perf **
Working Set Memory usage (evaluate): 1.60547 MB
Working Set Memory usage (load, bind, session creation, and evaluate): 1627.78 MB
Peak Working Set Memory Difference (load, bind, session creation, and evaluate): 2173.6 MB

@yskim1501 yskim1501 requested a review from a team as a code owner February 20, 2019 02:28
@yskim1501 yskim1501 changed the title Print Memory Peak Print Memory Peak Working Set Usage Feb 20, 2019
@yskim1501 yskim1501 requested a review from ryanlai2 February 20, 2019 02:28
}

std::cout << " Working Set Memory usage (load, bind, session creation, and evaluate): " << firstIterationWorkingSetMemoryUsage << " MB" << std::endl;
std::cout << " Peak Working Set Memory Difference (load, bind, session creation, and evaluate): " << firstIterationPeakWorkingSet << " MB" << std::endl;
Copy link
Copy Markdown
Contributor

@ryanlai2 ryanlai2 Feb 21, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we keep Working Set Memory Usage and Peak Working Set Memory Usage together for the (load, bind, session creation, and evaluate) metric? Moving line 296 up to line 287 and then adding a new line?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From Working Set Memory usage (load): 9.54297 MB
Working Set Memory usage (session creation): 12.1602 MB
Working Set Memory usage (bind): 1.09375 MB
Working Set Memory usage (evaluate): 1.26563 MB
Peak Working Set Memory Difference (from start to load): 9.21094 MB
Peak Working Set Memory Difference (from model load to session creation): 15.4883 MB
Peak Working Set Memory Difference (from session to bind): 0 MB
Peak Working Set Memory Difference (from bind to evaluate): 0.0820313 MB
Working Set Memory usage (load, bind, session creation, and evaluate): 24.0625 MB
Peak Working Set Memory Difference (load, bind, session creation, and evaluate): 24.7813 MB

to

Working Set Memory usage (load): 9.54297 MB
Working Set Memory usage (session creation): 12.1602 MB
Working Set Memory usage (bind): 1.09375 MB
Working Set Memory usage (evaluate): 1.26563 MB
Working Set Memory usage (load, bind, session creation, and evaluate): 24.0625 MB

Peak Working Set Memory Difference (from start to load): 9.21094 MB
Peak Working Set Memory Difference (from model load to session creation): 15.4883 MB
Peak Working Set Memory Difference (from session to bind): 0 MB
Peak Working Set Memory Difference (from bind to evaluate): 0.0820313 MB
Peak Working Set Memory Difference (load, bind, session creation, and evaluate): 24.7813 MB

@ryanlai2 ryanlai2 merged commit 5926f66 into master Feb 21, 2019
@martinb35 martinb35 deleted the user/kiyoung/peak-working-set branch June 21, 2021 18:59
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

Successfully merging this pull request may close these issues.

2 participants