[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Cache open repository per connection

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-07-02 04:25:54 CEST

On Wed, Jul 02, 2003 at 01:26:24AM +0200, Sander Striker wrote:
> > From: sussman@collab.net [mailto:sussman@collab.net]
> > Sent: Tuesday, July 01, 2003 5:43 PM
> > 2. As was already mentioned, because HTTP request is stateless, apache
> > opens and closes/syncs the repository (BDB environment) with
> > *every* request. (One user had write caching turned off on his
> > server; this caused his http checkouts to arrive about 1 file
> > every 2 seconds!) There's been discusion about keeping the
> > repository open for the whole TCP/IP "connection session", and
> > Sander has experimented with this, but it didn't seem to do much.

Bugs :-)

> +++ subversion/mod_dav_svn/repos.c (working copy)
> + /* Get the repository */
> + base_path = apr_pstrndup(r->pool, r->uri,
> + ap_find_path_info(r->uri, r->path_info));

Hmm. I'm not really sure what this is extracting from the URL. A clearer
comment might be helpful.

> + repos_key = apr_pstrcat(r->pool, "mod_dav_svn:", base_path, root_path);

Might want to put a ,NULL on the end there. Otherwise, your key is random
and will never get a cache-hit :-)

In any case, I'd recommend caching on the fs_path instead of the URI.

> + repos->repos = (void *)apr_table_get(r->connection->notes, repos_key);

I'd recommend using r->connection->pool's userdata instead of the notes.
Tables are not meant to store binary values; I'm not sure that it is very
reliable. You could (again) see corrupted data or cache misses.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 2 04:20:52 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.