Closed GoogleCodeExporter closed 9 years ago
Hi Rodrigo,
This is similar to what I just commented in Issue 30, more than likely what you
are seeing here is maximum heap space being reached, which will cause a big
reduction in performance, without necessarily falling over immediately. The
recommended approach is to use:
-Xmx8g
at a minimum if you are trying to inspect large traces using the find
functionality. Let me know your thoughts as regards this.
Original comment by ctjoreilly@gmail.com
on 24 Jan 2014 at 10:57
Hi Ciaran,
I see. Perhaps I confused slowness with freezing. I see now that sometimes it
takes quite a long time (almost 10 secs) just to select a node.
For the record, I added the -Xmx8g flag but it did not seem to make a
difference.
Original comment by rodrigob...@gmail.com
on 29 Jan 2014 at 11:28
Original issue reported on code.google.com by
ctjoreilly@gmail.com
on 4 Jan 2014 at 12:36