Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-13 Thread Branko Čibej
On 08.07.2012 17:47, Mattias Engdegård wrote: > The biggest surprise was that COW actually made the checkout slightly > slower, even though no "true" file copies were made. I'm not sure how > to explain this---perhaps everything is already in cache so the copies > aren't very expensive, or the COW

Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-11 Thread Mattias Engdegård
10 jul 2012 kl. 22.38 skrev Peter Samuelson: Whatever it is in the data path that makes it slower, it probably is not a fair comparison. Even though we normally don't want to do our own fdatasync(), it is fair to consider the additional I/O load that is generated by Subversion operations. Th

Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-10 Thread Peter Samuelson
[Mattias Engdegård] > The biggest surprise was that COW actually made the checkout slightly > slower, even though no "true" file copies were made. I'm not sure how > to explain this---perhaps everything is already in cache so the > copies aren't very expensive, or the COW operations are somehow >

Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-10 Thread Mattias Engdegård
9 jul 2012 kl. 18.08 skrev Daniel Shahaf: Thanks for clarifying. I'm not familiar enough with the library to have much more to say, but I thought I would point out svn_tristate_t (cf your maybe_t). Thank you, I didn't know about svn_tristate_t. I'll be sure to use it in any production versi

Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-09 Thread Daniel Shahaf
Mattias Engdegård wrote on Mon, Jul 09, 2012 at 09:40:48 +0200: > 8 jul 2012 kl. 19.26 skrev Daniel Shahaf: > > >Yes, please specify what the client used COW for. Was it for > >populating the working tree files from the pristine store? Was it for > >something else? > > It was only intended for

Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-09 Thread Mattias Engdegård
8 jul 2012 kl. 19.26 skrev Daniel Shahaf: Yes, please specify what the client used COW for. Was it for populating the working tree files from the pristine store? Was it for something else? It was only intended for that, but it's possible that the copying code is used for other purposes as

Re: Measured: btrfs COW and sqlite exclusive locking

2012-07-08 Thread Daniel Shahaf
Mattias Engdegård wrote on Sun, Jul 08, 2012 at 18:47:15 +0200: > Out of curiosity, I modified the svn client to use the btrfs > facility for fast file copies (copy-on-write, also known as > reflink), to see what benefits it might possibly give in terms of > performance and disk space. While at it,

Measured: btrfs COW and sqlite exclusive locking

2012-07-08 Thread Mattias Engdegård
Out of curiosity, I modified the svn client to use the btrfs facility for fast file copies (copy-on-write, also known as reflink), to see what benefits it might possibly give in terms of performance and disk space. While at it, I also measured the benefits of the sqlite exclusive locking th