I’m running Lua Glider (fully updated) on my Windows 64-bit, 32-gigs of RAM, i7 processor machine and Lua Glider’s performance is poor. When I start the application, it runs great, fast, and convenient. After 30 minutes of heavy use (coding, running sim, using tools, etc.) the performance begins to drop. Scrolling becomes jittery, windows become jittery, and moving the application around my screen becomes an issue. I end up getting the load circle after every key input and Lua Glider eventually freezes.
I’m getting really annoyed with this, it’s a great application with some aspects I cannot pass-up, but this problem is driving me away from using it. Hopefully there’s a solution.
Sorry about the delay in getting to you, we have been travelling recently.
Thank you for your detailed report. What you are describing seems to be a out of memory issue. We have been working on this issue for some time now and for performance reasons the entire code analysis database needs to remain in memory. The on-disk storage solution just is not fast enough yet. We will be implementing more aggressive measures to prevent this in an update soon.
In the mean time if you can give more memory for Glider to work with. By default it is set to 512mb but you can increase it to however high you want.
Open the Glider installation folder (usually C:\Program Files (x86)\M.Y. Developers\Lua Glider v 2.x)
Open etc->luaglider2.conf
search for -J-Xmx512m
change it to however much you like.
Save the file and restart Glider
These are temporary measures. A permanent fix to this problem will be coming soon.
I just went through with the fix so I can’t tell you if it worked or not (unless I respond again.) I’m glad you will be working on a more permanent solution, thanks again.
Yes, I am using Glider 2.0. The problem only starts to happen after using it for a long time… the CPU starts to be overloaded while the memory stays around 800mb. I have 16gb on my MAC, so it shouldn’t be any memory problem, but if glider limit itself to use only ~800mb and thens starts to do IO on disk, maybe this causing the cpu overload… But being honesty, I don’t think that is the problem, because all Glider starts to freeze… not only when editing the code… even trying to click on the top menu (File, Edit,…) is slow…
The problem only starts to happen after using it for a long time… the CPU starts to be overloaded while the memory stays around 800mb
Glider is running in a JVM so it will not use any more memory than what is alloted (in this case 800mb.) When it reaches this threshold the garbage collector frantically tries to reclaim memory resulting in a huge CPU spike. Eventually 99% of the CPU time is spent in GC and this triggers an out of memory condition and the heap is dumped to disk, which is probably the disk activity you are seeing. We are still trying to figure out why leaks occur for some but not for others. Perhaps it may be due to the size of the files or the number of projects simultaneously open?
I think the key is having more than one project in your projects tab. Previously I only had one project in there, then last night I added another project and worked on that and boom, got the slowdown.
Hope this helps in narrowing this down MYDevelopers.
Pre 2.0 I had dozens of Projects in the Project Tab, but when I installed to 2.0 decided to only have my active project - unfortunately still prone to slowdowns. Admittedly it happens far less frequently then pre 2.0 - but still occasionally happens, usually when I’m prone to leaving Glider running for days upon days.
My team are working on a large project with many larger files etc. Some config/script files can be above 2000 lines. And sometimes lua glider feels a bit slow even tho i have a 2013 macbook pro with 8gb ram.
Is there anything else you can do to enhance the perfromance of luaglider?
-Xms64m just sets the minimum memory allotment. This number usually is not relevant. The one you want to tweak is the Xmx512m.
-J-XX:MaxPermSize is the “permanent generation” memory area. This is java talk for things that are not garbage collected like classes, string literals, etc. Earlier version of Glider had issues with permgen but now you can probably get away with decreasing this value.
Sorry about the delay in getting to you, we have been travelling recently.
Thank you for your detailed report. What you are describing seems to be a out of memory issue. We have been working on this issue for some time now and for performance reasons the entire code analysis database needs to remain in memory. The on-disk storage solution just is not fast enough yet. We will be implementing more aggressive measures to prevent this in an update soon.
In the mean time if you can give more memory for Glider to work with. By default it is set to 512mb but you can increase it to however high you want.
Open the Glider installation folder (usually C:\Program Files (x86)\M.Y. Developers\Lua Glider v 2.x)
Open etc->luaglider2.conf
search for -J-Xmx512m
change it to however much you like.
Save the file and restart Glider
These are temporary measures. A permanent fix to this problem will be coming soon.
I just went through with the fix so I can’t tell you if it worked or not (unless I respond again.) I’m glad you will be working on a more permanent solution, thanks again.
