Community
Participate
Working Groups
I20060125-0800 Saving a file in my environment after adding a single blank to it seems to always touch a zip file which cost ~400ms. I will attach a trace
Created attachment 33636 [details] The HTML trace
Do you still see this problem if you give more memory to eclipse (e.g. double the -Xmx value) ?
I am running using 256 MB of heap space with a normal Eclipse dev workspace. Shouldn't this be enough. I will test with 512 MB.
The reading goes away when I specify 512 MB. Wouldn't it make sense to let the user control this. Now I have to specify a heap of 512 MB to get a bigger cache but this will also raise the size of the process space since it seems the VM will allocate memeory instead of doing a GC. I now have an allocated heap > 256MB although I was perfectly able to run with a heap of 256 MB.
Well, it doesn't seem you were running so well... <g> More seriously, we are thinking of changing the cache growing policy to be slightly more dynamic.
Fix to bug 121652 greatly improve Java model cache (I'm now able to self-host jdt.core using -Xmx64m). Please reopen if you still see this problem 3.2M5. *** This bug has been marked as a duplicate of 121652 ***