#42 performance problem

[esson]

Hello,

I am experiencing a major performance problem when
using the p4eclipse plugin. I am running win xp and
eclipse 3.0M7 on a 2GHZ proc w/ 512mb of memory. Our
project is large with respect to the amount of files it
contains (encroaching on 10,000). We have not
experienced any performance problems with the p4Win
client but the p4eclipse plugin renders eclipse
unusable. Are there any known performance problems
with large projects? I would like to help fix this
problem if possible.

- Jesse

[David Corbin]

Logged In: YES
user_id=1805

Please try the latest beta available at
http://p4eclipse.sf.net/beta . There have been some
performance improvements. Also, using .p4ignore files will
make a big difference if you have a lot of files (.o,
.class, etc) that are under your project directory that are
not under source control, and you have the "Show Added
Marker" preference enabled. You could also just turn off
this feature, as it can be a real time sucker in some
environments.

[esson]

Logged In: YES
user_id=1005870

Thanks for the quick response. Here is what I have done:

1. Uninstalled version 0.6.2
2. Installed the lated beta 0.6.20
3. Put a .p4ignore file in my build directory for *.class
and another one in a i18n image directory for *.gif
4. Shared my project with p4eclipse

P4Eclipse is spiking the processor when I right click on the
project in the package explorer. And the mem usage of
eclipse shoots from just under 100mb to just uner 300mb. Is
there an in memory cache? 200mb seems like a lot. I have
to disable the plugin for now...I haven't given up though
just running low on time.

-jK

[David Corbin]

Logged In: YES
user_id=1805

.class files should be ignored by default. Yes, there is an
in memory cache. Without it responsiveness woudl be
horrrible. (I know, you may feel ilke it is horrible
anyway). How large is your JVM Heap? I would have thought
that Eclipse without P4Eclipse would take close to 500 MB
for adequate responsiveness if you've got 10000 files.

I know I ran ~~2000 file project and I think I bumped the
JVM heap size up to 392MB, or maybe 512MB.