Trac slows when loading a proyect configured with a SVN repository which has empty folders

[mushomas@…]

TRAC 0.11.4, on RHEL5 with python 2.4 and SVN 1.4.6, using Postgres 8.1.11

I've got 14 Trac proyects on the same machine, all of then with the same SVN repository, but differente folder. Most of then work correctly, but a few ones go very slow.

I made a strace and I could see it was spending a lot of time reading SVN files.

I commented out the SVN lines in trac.ini, and it worked correctly and fast.

I revised the repo files and I found some empty folders, so I decide to put a file on then and resync the proyect, and now it works correctly and fast.

My question is: it's a trac o svn issue?

[Christian Boos]

• Create a test repository (testrepos) with empty folders.
• Verify that it exhibits the issue
• Do svnadmin dump testrepos > emptydirs.dump
• Then add files to the empty folders of that repository
• Verify that now the performance is OK
• Do svnadmin dump testrepos > nonemptydirs.dump

If you can successfully reproduce the issue with a test repository, then please upload those two .dump files so that we can try reproduce it as well.

Otherwise, if you can't reproduce it, it was likely some other local problem (maybe #8067).

[anonymous]

I've tryed what you said, but I couldn't reproduce my issue :(

In my production repository, I have deleted de files I added to the empty folders and I have made a new trac resync, and now it works fine again. I don't know what could be the problem…

I still have in production one trac with the issue, but i can't put here a dump of our SVN ;)

[Christian Boos]

I still have in production one trac with the issue, but i can't put here a dump of our SVN ;)

Look in the trac log file (eventually switch to at least the INFO level, see TracLogging). Do you see an INFO line saying "rev [xyz] != [abc]" for every request? (well xyz and abc being revision numbers, of course). If so, this is really a duplicate of #8067.

Which database backend are you using? If MySQL, which table engine? If not InnoDB, check the MySqlDb page for tips about why and how to switch.

[Christian Boos]

Sorry, just saw you said PostgreSQL 8.1.11. Still, #8067 can't be ruled out, please verify your log as describe above.

[anonymous]

Replying to cboos:

Look in the trac log file (eventually switch to at least the INFO level, see TracLogging). Do you see an INFO line saying "rev [xyz] != [abc]" for every request? (well xyz and abc being revision numbers, of course). If so, this is really a duplicate of #8067.

No, there aren't any line like that. It seems to resync OK. I've configured DEBUG log_level.

[Christian Boos]

Ok. You mentioned having done a strace, can you publish the strace output? Also, please give us more information about your setup. For example, do you use svn_authz extensively? Anything different between this problematic Trac environment and others?

[Christian Boos]

No feedback, closing.