Hi Felix, I think I tried this change few months ago, i remember I faced bugs in display. I don't remember exactly what but maybe I' m mixing with another place. It was in same jvm(no remote) Note that we advise users not to use gui mode for load testing.
Regards On Wednesday, December 30, 2015, Felix Schumacher < [email protected]> wrote: > Hi all, > > with bug 52694 and commit 1245602 the new method JMeterUtils#runSafe was > introduced, which uses SwingUtilities#invokeAndWait. > > I stumbled upon this while testing with gui and a report listener over > remote X, where the invokeAndWait lead to heavy lock contention. > > A simple test with 1000 threads and 500 loops using a simple java sampler > (0ms wait) and a Summary Report gives me > > invokeLater: ~100.000 req/s > invokeAndWait: ~30.000 req/s > > In my naive implementation I ignored the potential exceptions, that > invokeAndWait could throw, which we would have to catch using invokeLater > in other ways, but since invokeLater is used already in other places, that > should be no real problem. > > Any reason to use this instead of SwingUtilities#invokeLater? > > Regards, > Felix > > -- Cordialement. Philippe Mouawad.
