You can use it to track down your problem. You can download a Zing trial and play with it. It won't tell you anything about the various HotSpot specific TTSP paths (since most of those don't exist in Zing), but since you suspect mapped i/o based TTSPs, Zing should run into those just as much, and you'll get good TTSP coverage and clear-blame stack traces to play with.
On Tuesday, December 5, 2017 at 12:33:54 PM UTC+1, Mark Price wrote: > > >> In Zing, we have a built-in TTSP profiler for exactly this reason. >> > > I remember it fondly :) > > > > > -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
