Hello, i hope there is some other Eclipse Java programmer in this forum who can check whether this problem appears, too. I am not sure whether this is a problem related to parallels and its I/O performance or of Eclipse. I surely have this phenomenon only in my virtual machine. In my Windows XP machine, I am having serious trouble with everything that is JavaDoc related with the JDT. For instance, hovering over an identifer which would display Javadoc based information, takes about 2-3 minutes for the first time. Afterwards, the information seems to be cached. The same happens with the content assist/code completion. When the cursor is moved over an entry with associated Javadoc information, it takes again this long. Probably easiest to check, opening the Help contents also takes this long. Is any other Eclipse user seeing this? Unrelated to Eclipse, but maybe related: When i try to open the services view in the Windows XP systems, it also takes minutes to display the list. Is this normal for every Windows XP virtual machine installation? Thanks for your help!
Initial reply would be: why bother running this in a VM? Eclipse and Java both run fine in OS X; Seems to me that running in a VM is just incurring a performance penalty without much benefit. I develop mission critical Java applications in Eclipse (on OS X) with a team of seven developers; we have two developers running OS X, two in Linux, and the rest in Windows XP; code sharing and CVS access is transparent. As for your specific request, what hardware are you running on? How much memory does your machine have? How much memory is allocated to the VM? How much memory is allocated to Eclipse? Eclipse is a memory hog, and its default memory allocation is pretty minimal. When eclipse runs low on memory, performance is abysmal. We run eclipse with the following settings (update eclipse.ini on all platforms): -Xms256m -Xmx512m -XXermSize=64M -XX:MaxPermSize=128M The PermSize and MaxPermSize settings are important if you use any frameworks which use reflection heavily, such as Spring or Hibernate.
Hi buzzdat, thanks for your reply. I cannot use Macos X since i am using an eclipse-based product using a platform-dependant licensing scheme (with license server and so on). I just happenend to notice that this problem happens with vanilla-eclipse as well. Hence, i didn't specify this any further. I am using a macbook with 2GB ram. The virtual machine has been assigned something like 768M ram, parallels reserves something like 100M more. I will try your settings tomorrow, but i doubt they will change much. Eclipse runs fine as long as i don't use this Javadoc based stuff.
Still sounds odd. I'll try this out tomorrow to see if I can reproduce the problem. What version of eclipse are you running? What JVM? What 3rd party eclipse plugins or products are you using?
Eclipse 3.2.1, no plugins (removed them all before testing, workspace is also new), JRE 1.5 Update 9.
hey buzzdat, something was messed with my windows installation i guess. i created a new machine with a fresh windows installation and the problem went away. thanks for your time!
