Menu
I am doing TDD on a large Java project in eclipse and am finding it frustrating because every time I run a test I have to wait 30 seconds+ for eclipse to compile and refresh. I estimate that 80%+ of that time is spent refreshing.
Is there a way I can drastically reduce the amount of refreshing it is doing? I have looked at server other similar questions but I could not see anything that helps.
One way I reduced the compile refresh time was to split the unit tests and code into separate projects. There are 4,700 classes in the src project and 300 in the tests. I am running eclipse 3.5.1 on Java 1.6.0_17-b04 (eclipse.vm). My computer is running windows xp with 3.1 gigs of usable ram. The only plugin I have installed is subclipse.
606
I significantly increased the performance of Eclipse under 32-bit Windows by creating a RAM disk using the portion of the OS-unadressable memory as illustrated here.
If you have (or can increase to) 4GB of ram from your current 3.1 the same approach will quite possibly help you.
111
Have a look at the post I made here about eclipse.ini options: Eclipse IDE speed sluggish on Snow Leopard Macbook. Some of these might help you as they can adjust Eclipse environment settings (allocate more memory, etc). Also consider migrating your workspace to a faster disk :)
22
This could definitely be memory related. See one of:
They both give a good overview on Eclipse memory configuration, which I think will at least help with this issue.
40
It turns out there were build errors in the project that did not affect the tests or the code I was working on but were there none the less. When I resolved all build errors in my eclipse workspace the issue with long refreshes when away. This was tested on eclipse 3.5 and 3.6.
I feel a little foolish now :(, but from what I have seen professionally there are a lot of people with lingering IDE build issues.
1
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
