Working with Grails and GGTS requires a lot of memory provided by GGTS. The reason your IDE is getting slower by then is because it needs to do a lot of โstop worldsโ of garbage collections to get the memory it needs.
In particular, you can see that the first time you open a GSP file on your IDE ... then GGTS will darken. And you can see this in heap status at the bottom right of your IDE (enable it according to your preference). Each time the used memory is next to your 1 GB provided, your GGTS stops working for two or more seconds. After that, free memory appears again.
1 GB of memory for GGTS is ridiculously low - 2 GB should be minimal with Grails and Eclipse. But that's not all. GGTS has a memory leak using Grails tests and automatically creates. You can try to remove Unit and Integration tests from the project creation path. This is my trick to avoid slowdowns. But if I had to write Unit Tests, I have to restart GGTS periodically. (And I have 8192m written on my ggts.ini.)
Denny source share