I have the impression that the profiler is overloading the system with memory allocations for even moderately sized profile tests. This happens typically when the memory heap and execution flow analysis types are used.
Have there been any thoughts about implementing database support for storing the EMF data for the views to pull their data from, selectively? I know the monitoring project has a database support option. Could this be generalized into a generic feature that can be used by all projects and third parties? Henk Aling Wind River _______________________________________________ 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
