Marvin D. Toll wrote:
> In-line below ...
>> Is a [46,000 artifact] significantly larger than what others are
I don't do it on a daily basis, but I've done in<>out with projects of
that "size" (I put it in quotes, cuz how big is each file, etc.. Over
40 thou files though, I reckon).
Usually the task will complete, it just takes a "while".
In general, Eclipse just has a lot more overhead than the command line.
I really try to avoid using Eclipse for large imports though, just
because it has to do so much more work. And compared to running the
command line on the server hosting the repository, well, there's no
comparison. Hours long goes to minutes long.
Part of me thinks this is just The Way It Is, you know? An IDE has so
much more to worry about. With SQL, you run into the same type of
A large import is better handled by something that only has to worry
about that one task. :-/
Large imports can be done within Eclipse, I'll attest that, but
personally I avoid it whenever possible, just because of the overhead.
Last week I checked out 10 projects totaling around 8 gigs (90,000+
files) using Subclipse, and that went pretty smooth. I've done that a
few times recently (thank god for team project sets!) with good results,
so we're pretty solid there, for sure, which I think is more important
than importing that much info... Not an argument for not trying to get
better, mind you!
> Suffice it to say, if there is no formal load testing for Subclipse in place
> - I'm willing to put together a small test plan and archive the load test
> project for subsequent execution of the plan. (Of course I'm more
> interested in "typical" operations than the project "load" above.) This
> would not be definitive - however, if a particular operation showed 20%
> improvement with a new Subclipse release it could be cause for potential
This made me gasp. =] A happy gasp. While not big on writing tests
myself, I aspire to get more into it. I think they're a great idea.
And I'm a sucker for causes for potential celebration.
I wish I could commit to help, even with some simple ones- I can't cut
the mustard yet. I'll second that whatever you can do would be great.
And compliments on your posts, BTW.
-ps You might try playing with your settings some more, I've got this on
my windows eclipse shortcut: -vmargs -Xverify:none -XX:+UseParallelGC
-XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xmx256m -Xms256m
Don't know if any of those specific setting help with this stuff- with
less allocated, I'd think I'd hit the wall faster than you... maybe the
GC setting is helping? And These could be counter productive settings in
general... Dunno... I copied and pasted them from some random place.
A shot in the dark as per my MO. =]
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Sep 25 02:08:24 2006