- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For a typical profiling run, which takes about two hours to run, VTune takes around 50 minutes for the database conversion after the run completes before the results are posted. Checking 'top' on my shiny new 16-core Tigerton system, I notice that 15 cores are idle for 50 minutes while a single Java thread runs on a single core.
As the apostles of multi-threading, are you considering a multi-threaded version of VTune? Sure would be nice to see the results in 1/16th the time.
PS, PTU also uses single-threaded Java data conversion, but is faster.
As the apostles of multi-threading, are you considering a multi-threaded version of VTune? Sure would be nice to see the results in 1/16th the time.
PS, PTU also uses single-threaded Java data conversion, but is faster.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ron,
50 min database conversion is annoyingly long. Could you increase the sample-after value? This should improve the post-processing. Or do you actually need the precision of sampling?
Kind regards
Thomas

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