You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I initially posted this issue on the Plots.jl repo thinking it was a Plots issue, but as a matter of fact the problem appears for plain GR removing suspicion from Plots.jl
julia> @time using GR
0.183013 seconds (259.54 k allocations: 17.120 MiB, 10.09% compilation time)
julia> @time display(plot(rand(10)))
nothing
3.002674 seconds (1.04 M allocations: 60.426 MiB, 0.99% gc time, 13.93% compilation time)
julia> @time display(plot(rand(10)))
nothing
2.559036 seconds (208 allocations: 8.078 KiB)
So as you can see between the first and second invocation of the plot command, the timing is always around 2.5 seconds. Between the 2 invocations the I close the widow. If the window is not closed, the following timing is obtained:
There seems to be more system overhead on Windows when starting a Qt application and connect to it using a socket. On Linux and macOS caching and memory management is probably just better. Since this overhead is unavoidable, we made the separation in GR in the first place. So I'm wondering why you want to stop the gksqt application in running Julia session? Isn't it enough to minimize the plot window?
Hi,
Thanks for your answer.
Indeed I could just keep the window minimized and go with that,
but I think it is a bit sad especially now with native code caching in 1.9 that we still have this 2.5 seconds delay on the first plot. It kind of negates the progress made with pkgimages.
Of course I understand that if this is a windows issue, the problem might be hard to solve.
Hi,
I initially posted this issue on the Plots.jl repo thinking it was a Plots issue, but as a matter of fact the problem appears for plain GR removing suspicion from Plots.jl
So as you can see between the first and second invocation of the plot command, the timing is always around 2.5 seconds. Between the 2 invocations the I close the widow. If the window is not closed, the following timing is obtained:
Operating system : windows 10.
I have not observed this on linux.
Best,
Olivier
The text was updated successfully, but these errors were encountered: