How Can I Fix High CPU Usage (Javaw.exe) During RTC Query in eClipse?

I've searched through Jazz.net for answers to this issue, but couldn't find anyone asking the same question.

When I run a query in RTC which will return a large number of results (e.g., more than 1000), my eClipse client virtually freezes. I can periodically take actions, but the client is essentially unresponsive for several seconds at a time with only brief windows of interactivity. When I look at my running processes, javaw.exe is around 23-24%. Since I'm on a 4 core machine, this means it's essentially maxing out one of my CPUs.

What is causing this and is there any way to avoid it? I had thought that maybe limiting the number of query results in the eClipse client might be a work-around, but honestly it seems like it should be able to easily handle 1500 results. I don't know how to set limits on query results so if that's a viable option I'd be interested in knowing how to do this.