Subversion performance very slow under solaris

I am running 7051 under solaris. The subversion update process is very slow, sometimes it takes 5-10 minutes to update the changes tab. the command line version only takes a few seconds.

12 comments

Why doesn't IDEA on Solaris allow a CPU snapshot?

0

CPU snapshots are provided by YourKit profiler integration, though Solaris is supported. Maybe some unlucky combination of hardware/software...

0

Hello tim,

I am running 7051 under solaris. The subversion update process is
very slow, sometimes it takes 5-10 minutes to update the changes
tab. the command line version only takes a few seconds.


Could you please download the latest version of YourKit 6 from http://www.yourkit.com/
, put the libyjpagent.so for your version of Solaris into your IDEA\bin directory,
run IDEA and take a CPU snapshot of the update process?

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


0

i think i figured out what is going on with this - take the following directory structure:
~/projects/A
~/projects/B
~projects/...

Modules A and B are in my project, but non of the others.

All of the project and module files are in ~/projects. idea is scanning the entire directory structure looking for files to synchronize, even if they are not part of the project. in my case, i have 10-15 subfolders which are subversion'd but not part of this project, but they are being scanned by idea.

I think this is a bug, but maybe there is a configuration change to work around.

if i move my project files to a seperate empty folder everything works ok.

0

Hello tim,

i think i figured out what is going on with this - take the following
directory structure:
~/projects/A
~/projects/B
~projects/...
Modules A and B are in my project, but non of the others.

All of the project and module files are in ~/projects. idea is
scanning the entire directory structure looking for files to
synchronize, even if they are not part of the project. in my case, i
have 10-15 subfolders which are subversion'd but not part of this
project, but they are being scanned by idea.

I think this is a bug, but maybe there is a configuration change to
work around.


You should use Settings | Version Control to specify that only the projects/A
and projects/B directories are under Subversion, rather than the entire tree.
The default setting (VCS assigned to ]]>) means that all files
below the directory containing the project file and below all module content
roots are tracked by IDEA's VCS integration.

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


0

Dmitry - Why by default include the actual Project Root? Also, why isn't the actual Project Root a separate entry from the Module Root(s)?
Jon

0

Hello Jon,

Dmitry - Why by default include the actual Project Root?


This was a very common issue with previous versions of IDEA. We assume that
the most logical structure for a project is:
\Project
\Project\Module1
\Project\Module2
etc.

In Demetra and earlier versions, in order to work with files directly under
\Project, you had to create a fake module with \Project as a content root.
Now we wanted to get rid of this restriction, so we now also extend the versioning
to files under \Project. (In the next EAP build the project view will also
show files under the project base directory but not under any module content
root).

Also, why isn't the actual Project Root a separate entry from the Module
Root(s)?


You can create separate entries for module roots if you need to. By default
we have a single entry which covers everything, so that setting the project
VCS is as easy as possible.

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


0

Would it make sense to have a checkbox "Don't include files not under
module root"? I have
\Project
\Project\Module1
\Project\Module2
...
\Project\Module30

but I don't want a project that only uses Module1 and Module2 to have
the performance hit of having to scan/synchronise all the other modules.
R

0

Hello Robert,

Would it make sense to have a checkbox "Don't include files not under
module root"? I have
\Project
\Project\Module1
\Project\Module2
...
\Project\Module30
but I don't want a project that only uses Module1 and Module2 to have
the performance hit of having to scan/synchronise all the other
modules.


Yes, this would be possible. However, I'd like to get some more feedback
from others - is such a checkbox really necessary and the best solution?

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


0

Well for my part it would help with, e.g.
http://www.jetbrains.net/jira/browse/IDEADEV-17258
I can't speak for anybody else, of course.
R

0

I feel this area needs attention. I think Robert's suggestion would improve things but I feel like a more fundamental change might be warranted but can't say exactly what that would be.

0

I have a project with 2 modules. In the Version Control section, there is one entry for which implicitly includes my first module (not under the project root) but doesn't indicate that. There is a second entry for my second module and the Directory is blank - you have to hit Edit to see it is for the second module (bug?). Again, neither module's content root is under the Project Root. This is very unclear. Why should the 2nd module get an explicit entry but not the first? It seems like the Project Root should only be the Project Root - fine if it includes module roots that are contained underneath. The 1st module should also get its own entry. It sure seems like that should be decoupled from any module whose content root is not under the ]]>.

0

Please sign in to leave a comment.