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.
| Summary: | Add ability to mark certain state of memory results and display delta results again it with results obtained later | ||
|---|---|---|---|
| Product: | profiler | Reporter: | rasto1968 <rasto1968> |
| Component: | Base | Assignee: | Jiri Sedlacek <jis> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | gtzabari |
| Priority: | P3 | ||
| Version: | 4.x | ||
| Hardware: | PC | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
rasto1968
2005-01-18 09:44:40 UTC
Changing to feature. changing the summary to more broadly describe the feature. There are two possible ways to implement/use the delta function: - with (or without) automatically refreshing the results, a "delta" button would set the baseline and further display/get results would include the delta against it - with manual "get results", there could be a "get delta results" button, enabled if results were previously obtained, which would obtain new results, and include a delta against the latest results Planned for M6 Excellent news, I am looking forward to using this feature. I don't think now that we (or myself at least) will be able to accomplish this in the M6 time frame. Postponing to M8 We will no tbe able to implement this in the first release, but this is one of the top features for the further development, and should appear soon in the milestone releases of 2.0 Not in 1.0 Please re-evaluation. JVisualVM has some useful features for tracking memory leaks which Netbeans is missing such as showing the what memory remains unallocated between two snapshots and the number of generations it's been alive for. VisualVM uses a subset of the NetBeans profiler for profiling features, everything available in VisualVM is thus also available in NetBeans. Could you please better describe which feature do you use in VisualVM but can't use in NetBeans? There are two features which already provide almost similar functionality as described in this RFE, available both in NetBeans profiler and VisualVM: 1/ Reset collected results: this action clears all the data collected so far. When invoked before an action in profiled application and the action is then performed, the results are in fact delta results with only the data produced by the action. Note that profiling points can be used to reset the collected results to exactly define when reset is invoked. 2/ Compare memory snapshots: this action allows to visually compare two memory snapshots taken with the same settings. It creates a memory snapshot-like view with +/- diff values showing differences between the snapshots. We're still planning to add some kind of marking support to live results to provide runtime delta view, that's why this RFE is still open and valid. Sorry, I posted my last comment because I didn't notice that Live Results displays generational information if you configure the profiler to instrument *both* allocations and GCs. I agree that Netbeans' profiler supports the same functionality as JVisualVM. That being said, I still think the "compare two snapshots" feature isn't nearly as useful as it could be. Once you find a delta that looks suspicious there should be a way to "show allocation stacktraces" only against those deltas. Milestone cleanup: future->next This seems to have been forgotten and it would be REALLY handy. It seems like it would be pretty straight-forward as well. Can we get this into 7.0.1? Deltas are available for CPU and Memory live results since 8.1. For snapshots use the Compare action. |