| To: | "David Chinner" <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: tuning, many small files, small blocksize |
| From: | "Jeff Breidenbach" <jeff@xxxxxxx> |
| Date: | Mon, 18 Feb 2008 20:58:56 -0800 |
| Cc: | "Linda Walsh" <xfs@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=nBRdyZI5KbXG27XpG9sUgvJlb/rjHUyAJHkNafv0c+k=; b=qgr0qZm+PzIUzAbg5IkCdfxpgymGEBYdgfZfldSGzxkV6l0zEO3APbE+ipXjLTaZykLA+IKRvT09Znr2bYMgdZIw73NYtqQxP1J3V1yDVnMQDOfkRGkfinKj3ewuZ+avFiob07Dktv33/q4oQZL+lA4JXBA9qtw4OsUgd0kcDO4= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=eFqnp4nbXzpKF9S9ItMqybqwgtm9mN1IMvui2SLy1zIzY9IMZksvyKsP29gQj+SQAjfTSdhURspEjfCwkqWU4IDMI805M8KbMOdyS2mDvKUNMXZqrVdzopcqPEAjLQhqJBl4KhQvElSo172+d7kHjCqkS5vHAKiuIwagNCGCzd0= |
| In-reply-to: | <20080219024924.GB155407@xxxxxxx> |
| References: | <e03b90ae0802152101t2bfa4644kcca5d6329239f9ff@xxxxxxxxxxxxxx> <47BA10EC.3090004@xxxxxxxxx> <20080218235103.GW155407@xxxxxxx> <47BA2AFD.2060409@xxxxxxxxx> <20080219024924.GB155407@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Wow, this is quite some discussion. I went with Hannes Dorbath's original suggestion (appended), and am now several days into copying data onto the filesystem. It's conceivable to change course at this point, but awkward. Dave, you suggested biting the bullet and sacrificing capacity. Are we talking an overwhelming difference in read performance from random files - e.g. reducing the number of seeks by 2X? Finally, in answer to Linda's question, I don't forsee any appends at all. The vast majority of files will be write once, read many. A small fraction will be re-written, e.g. new contents, same filename. An utterly insignificant fraction will be deleted. >mkfs.xfs -n size=16k -i attr=2 -l lazy-count=1,version=2,size=32m \ >-b size=512 /dev/sda > >mount -onoatime,logbufs=8,logbsize=256k /dev/sda /mnt/xfs |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs: convert beX_add to beX_add_cpu patch(2.6.25-rc2), Timothy Shimmin |
|---|---|
| Next by Date: | website, Julissa Davis |
| Previous by Thread: | Re: tuning, many small files, small blocksize, David Chinner |
| Next by Thread: | Re: tuning, many small files, small blocksize, Peter Grandi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |