Slow refactory/deleting [message #508547] |
Tue, 19 January 2010 12:09 |
Marco Messages: 7 Registered: January 2010 |
Junior Member |
|
|
Problem:
Sometimes eclipse is really slow with activating the refactory/delete (from the package explorer.) (edit: refactory of function names, delete of classes)
To be more specific there's a large time (1 to 5 minutes) before the question appears "Do you wish to delete .....". The deleting itself is rather quick.
Is it doing some legitimate work? (what and can it be shown in the progress view)
and a few quick answers to questions I expect:
- highest version of eclipse where I did not see the problem was 3.3.2.
- I gave eclipse enough memory. It's only using 500M of the 1000M available. (It was worse without this though)
- Seen with the EE and Java editions of eclipse.
- My workspace has multiple open projects (all different CVS modules) working together (well, more or less).
Thanks in advance,
Marco
[Updated on: Thu, 21 January 2010 08:17] Report message to a moderator
|
|
|
Re: Slow refactory/deleting [message #511661 is a reply to message #508547] |
Tue, 02 February 2010 13:24 |
Marco Messages: 7 Registered: January 2010 |
Junior Member |
|
|
I just noticed with refactory of function names it also sometimes can be slow. (I used the Alt-Shift-R on a function name)
But when I do this, a sort of progress appears at the button of the window where it tells me that it's checking preconditions, looking for references etc. (It also has a red button to stop the process.)
edit: This with Eclipse 3.6 M4 EE edition
It's also relative slow sometimes and also seems to occupy a single processor on my machine for 100% for some time
Could this also be happening from the package explorer, just without the added progress view (toolbar)?
Marco
[Updated on: Tue, 02 February 2010 13:28] Report message to a moderator
|
|
|
Re: Slow refactory/deleting [message #514949 is a reply to message #508547] |
Wed, 17 February 2010 10:04 |
Marco Messages: 7 Registered: January 2010 |
Junior Member |
|
|
I think I found out a big part of the problem.
in my case memory exceptions in Eclipse were happening while initializing my workspace, which are not handled nor displayed in any way. (not without some searching)
I've reset the ini file to the original version, added the same memory settings through command line and at least those exceptions upon starting are gone.
For now, it looks to be more stable.
A question I now have: Is there a view that displays problems eclipse has (other than the console that comes with -debug)
Thanks for reading,
Marco
edit:
it's still "slow" for some actions, but at least they finish (roughly within a minute) using 50% of CPU (dual core)
The debug console does not show any exceptions when this happens, the jconsole does not show which thread is using the CPU. (can it)
[Updated on: Wed, 17 February 2010 13:21] Report message to a moderator
|
|
|
|
Re: Slow refactory/deleting [message #515237 is a reply to message #515110] |
Thu, 18 February 2010 09:33 |
Marco Messages: 7 Registered: January 2010 |
Junior Member |
|
|
Eric Rizzo wrote on Wed, 17 February 2010 13:04 |
Open the Error Log view. You can also view the log on your file system:
<workspace>/.metadata/.log
Hope this helps,
Eric
|
Thank you, I'll keep an eye on it.
Looking back into it's history it does not show those memory errors though.
After playing around a bit it looks like increasing the size of the "eden" memory space has been effective in solving more of my problems.
I currently set this on the command line:
-vmargs -Xms1250m -Xmx1250m -Xmn850M -XX:ReservedCodeCacheSize=64m -XX:MaxPermSize=256m -XX:+UseParallelGC -Dcom.sun.management.jmxremote
Thanks,
Marco
[Updated on: Thu, 18 February 2010 09:33] Report message to a moderator
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 8.46748 seconds