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: | Cannot profile complete application with app server startup profiling | ||
---|---|---|---|
Product: | profiler | Reporter: | syellam <syellam> |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | VERIFIED WONTFIX | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
syellam
2006-06-18 18:34:05 UTC
You are right - the profiler wouldn't work with more than 65k methods instrumented. This is based on the profiler architecture and is not an easy thing to change. Anyway, such number of instrumented methods would generated overhelming quantities of data so the recommended way of doing the profiling is to focus on certain area of the profiled application. This can be done eihter by instrumentation filters or root methods. More information about filters and root methods can be found in the profiler documentation. Actually, I can't see any reason why you would want to profile application server startup, unless you are an application server developer. In your case (having 2 EJBs with custom methods) I would prefer selecting the custom methods as profiling root methods thus profiling only your part of code and leaving the infrastructe intact. If you insist on profiling the whole application server codebase I would recommend setting at least "Exclude Core Java Classes" filter which brings down the number of instrumented methods to something like 17k on my system. As noted above, getting all the data isn't much usable, I don't think you are able to evaluate them all. This is why Part of Application profiling mode is available in NetBeans Profiler to finetune the scope of profiling. This is not a bug, in fact. I created an enhancement request #82315 based on this report. Verified as wontfix |