- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I've been using Vtune for lots of profiling work. But never thought of use it to profile the system time. I'm wondering is it possible to do that? For example, I have a program running for 10 seconds and among which total 2 seconds are system calls. I want to know how the 2 seconds are used. And, if I fetch this program to Vtune, the runtime could be very different depends on my collector setting. Let's say now it's 20 seconds. But I can not find the exact system time then.
Anybody has experience on this? To profile the system time.
Regards,
Nicol
I've been using Vtune for lots of profiling work. But never thought of use it to profile the system time. I'm wondering is it possible to do that? For example, I have a program running for 10 seconds and among which total 2 seconds are system calls. I want to know how the 2 seconds are used. And, if I fetch this program to Vtune, the runtime could be very different depends on my collector setting. Let's say now it's 20 seconds. But I can not find the exact system time then.
Anybody has experience on this? To profile the system time.
Regards,
Nicol
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VTune EBS would capture the system time of your program, and any other processes present, in the modules responsible. Those modules probably don't have adequate debug symbols to show you precisely what's happening, or distinguish what they may be doing on behalf of your program from other usage. For certain Windows system .dlls, helpful .pdb or equivalent may be available.
When a significant amount of time is spent in system libraries, it is helpful to make a static link for profiling purposes, as that should capture those particular functions as part of your program, usually with identification of the function responsible. This can help distinguish true system time from those system run time libraries.
Perhaps, for completeness, I should mention the openmp and MPI profiling libraries provided with Intel software tools. Even the dynamic versions of those libraries capture the time associated with those function calls. If you are using one of those facilities, these profiling libraries are an important step in analyzing time spend outside your own compiled code.
When a significant amount of time is spent in system libraries, it is helpful to make a static link for profiling purposes, as that should capture those particular functions as part of your program, usually with identification of the function responsible. This can help distinguish true system time from those system run time libraries.
Perhaps, for completeness, I should mention the openmp and MPI profiling libraries provided with Intel software tools. Even the dynamic versions of those libraries capture the time associated with those function calls. If you are using one of those facilities, these profiling libraries are an important step in analyzing time spend outside your own compiled code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tim18
VTune EBS would capture the system time of your program, and any other processes present, in the modules responsible. Those modules probably don't have adequate debug symbols to show you precisely what's happening, or distinguish what they may be doing on behalf of your program from other usage. For certain Windows system .dlls, helpful .pdb or equivalent may be available.
When a significant amount of time is spent in system libraries, it is helpful to make a static link for profiling purposes, as that should capture those particular functions as part of your program, usually with identification of the function responsible. This can help distinguish true system time from those system run time libraries.
Perhaps, for completeness, I should mention the openmp and MPI profiling libraries provided with Intel software tools. Even the dynamic versions of those libraries capture the time associated with those function calls. If you are using one of those facilities, these profiling libraries are an important step in analyzing time spend outside your own compiled code.
When a significant amount of time is spent in system libraries, it is helpful to make a static link for profiling purposes, as that should capture those particular functions as part of your program, usually with identification of the function responsible. This can help distinguish true system time from those system run time libraries.
Perhaps, for completeness, I should mention the openmp and MPI profiling libraries provided with Intel software tools. Even the dynamic versions of those libraries capture the time associated with those function calls. If you are using one of those facilities, these profiling libraries are an important step in analyzing time spend outside your own compiled code.
I see some other profiling tools do report meaningful results for my same case(some stall time report). I'm trying to find equivalent function in Vtune.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page