Hi everyone, I'm to implement a rules engine for a profiler. The end aim is to be able to describe you performance rules in Eclipse, exectue a profiling session and have a report generated saying if the rules were satisfied. A basic example is a constraint on the execution time of a method.
It seems that the best way to do this based on what is currently available in TPTP is to watch the EMF model and analyse it. However I have the following problems: * There is no uniform way to find out when a trace is occuring and grab the current trace model. I can subscribe to ProfileEvent events to find out when a profile is occuring but the only way I have found to grab the corresponding trace model is use TraceUtil.getMofObject() which returns the currently selected element in the Profiling Monitors view. This feels like a bit of a hack * The most appropriate time to do the analysis is as new profiling events occur (e.g method entry, method exit) however there is no way to hook into this. Each different type of profiling event is handled in it's own way and I have not been able to sucessfully use the Notification API in the EMF model for a trace to catch when events such as method innvocations are occuring. Guru mentioned that someone had written something similar to my idea but specificially for memory analysis. I haven't been able to found this in CVS, could someone point me to the correct module. Thanks in advance for the help. Regards, Neil Dunn _______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
