This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 51542 - Allow storage/retrieval of profiling data
Summary: Allow storage/retrieval of profiling data
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on: 51274
Blocks: 55451
  Show dependency tree
 
Reported: 2004-11-16 04:50 UTC by jchristi
Modified: 2007-02-12 22:09 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jchristi 2004-11-16 04:50:57 UTC 
It would be immensely cool and greatly enhance the
usefulness of this tool if one could save off to a
file all the underlying data for all the graphs
and profiling result views, so that one could
later re-load this data and continue additional
analysis.... or send off to someone else for help
to analyze performance problems.

Also it would allow for automated profiling runs
to be done, a 'nightly profile', and the results
to be saved to file so a human could come back,
load the file and review the collected performance
data.
Comment 1 jchristi 2004-12-04 19:04:17 UTC 
The profiler in the Hyades project http://www.eclipse.org/hyades/ does
the same thing, allows profiling information to be stored so it can be
browsed with the UI at a later point in time as well.  

This has been a very useful capability.
Comment 2 iformanek 2005-01-13 13:52:42 UTC 
We would like to change the way results are held in memory, which 
should allow a lot of things to be implemented:
- more efficient "live data" display (currently implemented as 
periodic "Get results"
- saving/reopening results data
- ability to more efficiently browse/search the results
- ability to more efficiently visualize the results (e.g. not 
collapse the trees, compute aggregated data only on demand when a 
tree is expanded, etc.)
Comment 3 iformanek 2005-01-13 13:56:52 UTC 
Will be done in 1.0
Comment 4 mishadmitriev 2005-02-16 00:51:47 UTC 
Planned for M7. The internal implementation depends on issue 51274 
implementation.
Comment 5 mishadmitriev 2005-02-16 16:57:37 UTC 
To clarify the dependency: issue 51274 should address the current 
problem of quick obtaining and economic storage of CPU profiling data 
for all profiled threads at once. This will require modification of 
the internal format for storing presentation-level CPU profiling 
data. This format is going to be a "flat" one, which will make it 
easy to save/retrieve from disk, which is a subject of this issue 
(51542).
Comment 6 mishadmitriev 2005-04-29 19:33:41 UTC 
Planned for M7, though likely for CPU profiling data only.
Comment 7 mishadmitriev 2005-05-12 00:27:24 UTC 
Done for CPU profiling data, as the one where capability to save/retrieve data
seems most essential. Will probably need to open another issue for memory data
snapshots, if it's demanded.
Comment 8 iformanek 2005-05-12 12:42:37 UTC 
I'll keet this one open, as this is not specific for CPU results.
Comment 9 iformanek 2005-05-16 13:46:57 UTC 
In progress for M7
Comment 10 iformanek 2005-06-19 11:13:08 UTC 
Fixed in M7
Comment 11 ehucka 2006-10-09 12:09:31 UTC 
Verification of old issues.
Comment 12 Alexander Kouznetsov 2007-02-12 22:09:31 UTC 
Closing old issues.