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.
Based on package/class/method name report back some higher level values for how much time was spent in what sorts of processing. In other words, a reporting filter/aggregation feature. The user could select pre-defined sets of "functionalities." As an example, a "SOAP functionality" feature would be defined with the following root methods: Parsing + SOAP protocol handling, the sum of the following entry points : com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher#toMessageInfo com.sun.xml.ws.protocol.soap.server.SOAPDecoder#doMustUnderstandProcessing com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher#getSOAPMessage Serialization : com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher#makeSOAPMessage Time spent in the endpoint itself: com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher#invokeEndpoint Sending a reply (network there): com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher#sendResponse Then when the "SOAP functionality" filter is chosen by the user the Profiler would report CPU time in a report that contains something like: Parsing + SOAP protocol handling: 25% Serialization : 20% Time spent in the endpoint itself: 10% Sending a reply (network): 45% Having stacked/aggregation of functionality profiles would be the ideal feature. For example, the user could say "This is a J2EE application, could you present to me the time spent in each J2EE component?" Examples would be: Web Container, EJB, DataBase, Transaction, JMX, etc. So J2EE would be a profile of functionalities composed by the aggregation of finer profiles (EJB, db, etc). The SOAP profile described above could be a profile contained by the Web container profile, etc. Another example would be: "This is a J2SE application that accesses a web service for data that is then drawn using Java2D." The user might want to know how much time is spent marshalling/unmarshalling the data, how much time in rendering, etc.
This is partially addressed by "Area-of-interest" graphs. I will add more categories to better reflect the requirements of this enhancement.
Target milestone cleanup.
Milestone cleanup: future->next
It's rather probably this will make it to 7.2
changing owner