Comparison of PgSQL Performance on HAMMER and UFS

[Jan.Lentfer at web.de]

Zitat von Matthew Dillon <dillon at apollo.backplane.com>:

    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
I redid the tests as suggested and with a slighlty different test  
setup. Results attached. Next step: Redo the tests on -DEVELOPMENT.

Regards,

Jan



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Attachment:
HAMMER_pgsql.pdf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdf00001.pdf
Type: application/octet-stream
Size: 15269 bytes
Desc: "Description: Adobe PDF document"
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20091021/6a1b9b50/attachment-0021.obj>