From: | Jan.Lentfer@xxxxxx |
Date: | Wed, 21 Oct 2009 16:25:58 +0200 |
I'd like to see how those results compare with the various MPSAFE sysctls turned on, and also with fsync disabled (so we can get an idea how badly fsync effects write transactions, since we know fsync is very expensive on HAMMER):
vfs.getattr_mpsafe=1 vfs.read_mpsafe=1
And
vfs.hammer.fsync_mode=2
And also with the recent buffer cache work on master. The meta-data for a 5GB dataset should be cachable but prior to the work buffer cache data was being thrown out of the backing VM page caches too quickly.
Another thing we know about HAMMER is that the initial B-Tree layout is pretty horrible. It takes a reblocking pass to fix it up. It shouldn't effect a dataset that small with the cache priorities fixed in master, though.
-Matt
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Attachment:
HAMMER_pgsql.pdf
Description: Adobe PDF document