speeding up the launch time of Eclipse

I can only say that Eclipse 3.3 on XP starts up in seconds (with JAVA 1.6.2).
As far as I know it is not possible to keep significant parts of Eclipse in memory
as the T-bit (sticky bit) in the mode only works for binary parts,
not for the .jar parts.
But of course you could read those files into cache at boot time.
Finally, you could disable some parts of Eclipse, like team, but the difference will be small.
;JOOP!

Hello Sciuriware,

What is the T-bit (sticky bit)?
How to "read those files into cache at boot time"?

1) UNIX and UNIX-derived Operating Systems use the in 1970 filed patent by Ken Thompson sticky
file mode, that is, binaries with a mode of 1000 octal in combination with their execution mode
(e.g. 1711 = -rwx--x--t) stay in memory after their first execution to speed up new executions.
Later UNIX versions use this mode on directories to forbid removal of files by a non-owner.

2) Any program can simply read a file entirely (even wasting away the input), after which the
file is surely in the system cache for some time. This applies to all UNIX-derivates and all Windows flavors.

;JOOP!

I upgraded to Eclipse 3.2, but it still takes 55 seconds to launch (mainly loading the workbench).

Reading the eclipse files at the beginning didn't have much impact. Maybe the total size is too big to keep it in the cache.

I could not upgrade to Java 1.6, because it is still not available for MacOSX (I think).

One minute to launch Eclipse is awful.
How to speed it up?

P.S.: I have:

3GHz INTEL Pentium-4, 2Gb memory, 7200 rpm IDE disks, Windows XP Home, JAVA 1.6.2, Eclipse 3.3
resulting in a startup in 12 seconds for the first time
and average 7 seconds if restarted within 10 minutes (cache).

;JOOP!

B?

B?
I don't understand your question.

You rated the answer B.

Eclipse is still taking 1 minute to launch.