Hi Rob,
I have tried put GC.disable() and GC.enable() around the
rendering call and it made no difference.
On Friday, 31 May 2013 at 02:13:36 UTC, Rob T wrote:
I don't know if this is the case with the code in question (I
have not looked at it), but sometimes there will be a
significant effect on performance caused by the use of the
garbage collector. This is an area in need of radical
improvements.
You have to minimize situations where there's a lot of
allocations going on while the GC is enabled because that will
fire up the GC more often than is required and it can slow down
your app significantly; A 2x or more performance penalty is
certainly possible. It can also make performance unpredictable
with large delays at inappropriate points in the execution.
BTW, you should post questions like this into d.learn rather
than in the general discussion area.
--rt
