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

Re: SQL backend database scheme

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 1 Apr 2010 14:56:54 -0400

2010/3/31 Jan HorŠk <horak.honza_at_gmail.com>:
> 30.3.2010 13:55, Philipp Marek wrote:
>> †* Furthermore, how about allowing the plain data to reside in files?
>> † †Would make the database much smaller, and then these data blocks
>> † †could possibly be shared among multiple repositories.
>> † †(Really easy, too, if they're named by their SHA1, for example).
>> † †That should allow for zero-copy IO, too (at least for sending data).
> The question is, how much faster it would be.. I would like to make a simple
> test to simulate this soon and estimate the percentage difference..

My gut says "not that much faster". In most scenarios, the network
bandwidth between the client/server will be the bottleneck. Reading
the data off a disk (rather than from a DB) is not going to make the
WAN connection any faster.

On a LAN, you might have enough network bandwidth to see bottlenecks
on the server's I/O channel, but really... I remain somewhat doubtful.

I'd go with the "store content in the database" until performance
figures (or a DBA) demonstrates it is a problem.

Received on 2010-04-01 20:57:26 CEST

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