On Fri, Feb 26, 2010 at 7:44 AM, Matthew Beets <mbeets_at_gmail.com> wrote:
> I am experimenting with some of the new options in 1.6 and I'm trying to
> investigate any benefits using memcached may provide.
Not to discourage you from trying, but the others that have done the
same did not see any tangible benefits. Most of these users were
already using pretty fast disk systems for their repositories, so
perhaps if yours are on a single spindle or something and you have a
lot of RAM for the cache you might see different.
> I am trying to get this running on Windows XP 32 bit with CollabNet
> Subversion Server 1.6.9 (http://www.collab.net/downloads/subversion/)
> and NorthScale Windows port of memcached 1.4.4
> I am using both the CollabNet svn command line client and TortoiseSVN 1.6.6
> I install Collabnet server, start the subversion windows service and create
> a test repository using svnadmin at the command prompt.
> I run the memcached.exe that comes in the NorthScale package (no command
> line options. It is supposed to be listening on port 11211 by default.)
> I navigate to the fsfs.conf file for my test repository and uncomment the
> line "first-server = 127.0.0.1:11211"
> Now when I try to checkout my empty test repository ( using "svn checkout
> svn://localhost/test C:\svntestcheckout" ) I get the message:
> svn: apr memcache library not available
It sounds like when the CollabNet httpd binaries are compiled there is
something special that has to be done to compile in memcache support.
It is also possible the httpd/apr just does not support this on
Windows. The latest CollabNet binaries include httpd 2.2.14. You
could try downloading that version of httpd from Apache and see if it
is compiled differently. Just use the mod_dav_svn that CollabNet
provides with those binaries.
Received on 2010-02-26 16:55:24 CET