Re: question on performance evaluation of beagle's indexing
- From: "Arun Raghavan" <arunissatan gmail com>
- To: "D Bera" <dbera web gmail com>
- Cc: Nitin Agrawal <nitina a gmail com>, dashboard-hackers gnome org
- Subject: Re: question on performance evaluation of beagle's indexing
- Date: Wed, 2 Apr 2008 20:07:41 +0530
On 02/04/2008, D Bera <dbera web gmail com> wrote:
<snip>
> Beagle stores its bookkeeping information per file in the extended
> attributes of the files or if that fails, in an sqlite database. There
> is a folklore that using the extended attributes is significantly
> faster than the sqlite database (disk access vs sqlite access). But
> depending on disk I/O speed and other system load, sqlite access could
> sometimes be faster IMO. For simplicity we ignore the tradeoff and
> always suggest and prefer extended attributes over sqlite. You can
> force sqlite by setting BEAGLE_DISABLE_XATTR.
Note that the xattr performance is also FS-dependent. Different
file-systems have different ways of storing xattrs. Ext2/3 store it
either in the inode, or in a separate block if more space is required.
ReiserFS stores each xattr as a (hidden) file in /.reiserfs_priv (and
counts on its tail-packing for efficiency), and XFS has 3 methods
(in-inode for small numbers, and using B+ trees in the most complex
case -- the method depends on the number/size of xattrs, IIRC).
Cheers,
--
Arun Raghavan
(http://nemesis.accosted.net)
v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056
e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]