5650 unusable with Perforce server on high-latency network

By the way, I'm not sure whether this would have an effect, but I do have over 6000 files listed in the "Unversioned Files" section due to a significant amount of code generation.

Thanks,
-Bruce

Hello brucet,

That's it. There's indeed a significant slowdown with huge amount of unversioned
or locally deleted files. Could these be somehow excluded from versioned
directories?

-

Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

By the way, I'm not sure whether this would have an effect, but I do
have over 6000 files listed in the "Unversioned Files" section due to
a significant amount of code generation.

Thanks,
-Bruce

That's it. There's indeed a significant slowdown with huge amount of unversioned
or locally deleted files. Could these be somehow excluded from versioned
directories?

No, unfortunately these cannot be excluded because the majority are generated java files that are a part of the project, but which we specifically do not want to check in to perforce.

There are also some non-critical generated artifacts that reside in the source directories due to a somewhat sloppy build process. This might be possible to address some day, but would be a big project. It might be possible to exclude some of these if exclusions could be done via regular expressions, but this would be pretty tedious.

If the unversioned files are the problem, maybe there could be an option to turn off the tracking of unversioned files?

Thanks,
-Bruce

No, unfortunately these cannot be excluded because
the majority are generated java files that are a part
of the project, but which we specifically do not want
to check in to perforce.

I'm not familiar with perforce, but I imagine it has some kind of ignore mechanism a la .cvsignore or svn:ignore. Can't you add the generated files to to perforce's ignore list, so they don't show up as unversioned files?

Hmmm, I looked around a bit for this, but could not find any equivalent functionality.

-Bruce

Hello,

Many months after I encountered this problem on release 5650, I have just tried this out again on 6148, and am having all the same problems.

Because we use code generation, we have a scenario where we will forever have a large number of unversioned files which we do want to remain in the project (this is in the thousands). It sounds like IntelliJ has a serious performance problem when faced with large numbers of unversioned files.

Is there any way to handle this? Maybe a toggle for whether unversioned files should be tracked?

Thanks,
-Bruce

Hello brucet,

Many months after I encountered this problem on release 5650, I have
just tried this out again on 6148, and am having all the same
problems.

Because we use code generation, we have a scenario where we will
forever have a large number of unversioned files which we do want to
remain in the project (this is in the thousands). It sounds like
IntelliJ has a serious performance problem when faced with large
numbers of unversioned files.

Is there any way to handle this? Maybe a toggle for whether
unversioned files should be tracked?

One performance issue related to large number of unversioned files is fixed
in 6.0.5 EAP. In Selena, there's support for ignoring unversioned files,
which lets you specify that files in certain directories or files matching
certain masks should not be reported as unversioned. This should help even
further.

As usual, CPU snapshots are always welcome - it's possible that they will
reveal some problems which haven't yet been addressed.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

Excellent, the problem seems to be completely resolved in the Selena 6708.

Thanks!
-Bruce