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 automatically perform calibration before each profiling session | ||
---|---|---|---|
Product: | profiler | Reporter: | Jiri Sedlacek <jis> |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | anebuzelsky, yjoan |
Priority: | P4 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Jiri Sedlacek
2005-08-03 18:14:58 UTC
Note that dynamic CPU perf switching isn't from far the only case. I often start the profiler on a wide variety of OS / hardware couples (Solaris, Linux on either servers or tinier blades) On UNIX systems the calibration output is stored in the user home directory (e.g. $HOME/.nbprofiler/machinedata.jdk16 for JDK 6) and my home directory is unique, accessed whatever the UNIX system I use is. It means if I forget to manually remove calibration data, I will use let's say Linux desktop data for a profiling session of a fat server with Solaris. Milestone cleanup: future->next |