2009. 3. 31. 05:00
[code/tip]
eclipse 빨리 실행하기
from: http://www.raibledesigns.com/page/rd/20030312
I changed my shorcut icon (Win2K) to have the following as it's target:
eclipse.exe -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xmx256m -Xms256m
Eclipse now starts in a mere 6 seconds (2 GHz Dell, 512 MB RAM). Without these extra settings, it takes 11 seconds to start. That's what I call a performance increase! (2003-03-12 09:32:04.0)
from: http://www.raibledesigns.com/comment.do?method=edit&entryid=065039163189104748672473500018
I tried this out, but the memory settings don't seem to have anything to do with startup time.
18 seconds - "eclipse.exe"
13 seconds - "eclipse.exe -vmargs -Xverify:none"
12 seconds - "eclipse.exe -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xmx96m -Xms96m"
It's only the Xverify:none parameter which has a noticeable effect on reducing startup time. On the java website I found that this parameter turns off bytecode verification ( http://developer.java.sun.com/developer/onlineTraining/Security/Fundamentals/Security.html ), although the default is supposedly "only verify classes loaded over the network".
from: http://www.raibledesigns.com/page/rd/20030312
I changed my shorcut icon (Win2K) to have the following as it's target:
eclipse.exe -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xmx256m -Xms256m
Eclipse now starts in a mere 6 seconds (2 GHz Dell, 512 MB RAM). Without these extra settings, it takes 11 seconds to start. That's what I call a performance increase! (2003-03-12 09:32:04.0)
from: http://www.raibledesigns.com/comment.do?method=edit&entryid=065039163189104748672473500018
I tried this out, but the memory settings don't seem to have anything to do with startup time.
18 seconds - "eclipse.exe"
13 seconds - "eclipse.exe -vmargs -Xverify:none"
12 seconds - "eclipse.exe -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xmx96m -Xms96m"
It's only the Xverify:none parameter which has a noticeable effect on reducing startup time. On the java website I found that this parameter turns off bytecode verification ( http://developer.java.sun.com/developer/onlineTraining/Security/Fundamentals/Security.html ), although the default is supposedly "only verify classes loaded over the network".