|Re: [tracecompass-dev] Java VM out of memory with TraceCompass reading generic CTF|
Be assured, you are _not_ pushing Trace Compass past its intended
use, not at all. That is exactly what the tool is intended for:
analyse any kind of trace.
That said, with new use cases like this one, there may be unforeseen bottlenecks, and some analyses are known not to scale (the segment store ones, like the System Call latency analysis, or some XML analyses). Do you have any of those open? What views are opened in your UI that might cause this OOME? Try to close all views (except maybe the statistics) and see if it still causes the error. And then reopen them one by one to see if one of them seems to be problematic. As for the number of streams, I recall some people have done tracing on a Xeon Phi with 256 cores, so I think there were 256 streams and it worked well, so that should not be the problem.
You can also open a bug on bugzilla and attach the trace, then we can investigate what may be the problem with this specific trace.
On 2017-04-09 02:01 AM, Rocky Dunlap wrote:
Back to the top