A few of my various Eclipse 3.5 (actually SpringSource ToolSuite 2.2) workspaces are painfully slow when building, and I have a suspicion this is because they are continuously grabbing network resources from over the internet (e.g. schemas), whereas other workspaces, with similar content, are fine. Tracking these down is problematic.
Does anyone know how to track these down, if this is in fact what’s happening? Something like a log file which tracks each URL being accessed, or something of similar utility.
Edit: I should have mentioned that I’ve considered using a packet sniffer like Wireshark, but Eclipse generates a lot of traffic, and it’s hard to see the wood from the trees. I’m looking for something higher level.
Edit: In the end, it turned out that SpringSource ToolSuite was doing some highly inefficient classpath scanning, slowing things to a crawl. No network access at all, it just felt like that kind of performance hit.
You could simply look directly at the wire, e.g. using Wireshark or using a HTTP proxy like loxy (never tried this one though).
Most likely it’s a single resource where the connection times out. This should be pretty easy to spot (i.e. search) and remove from your workspace.
At the Java level, you might use a profiler or instrumentation to track down methods that take a long time to complete.