Zbr's days.
March
Sun Mon Tue Wed Thu Fri Sat
           
19
         
2008
Months
Mar
Sep
Oct Nov Dec

About TODO Blog RSS Old blog Projects Gallery Notes

Wed, 19 Mar 2008

Temptation is over...

One man, 12 nights (13 days), one bottle of cuban rum and little bits of scotch whisky, 82 'House M.D' series... feels good.

Meanwhile got three 2-way Xeon servers with 2-4 (I forgot) gigs of RAM and gigabit link between them. Not bad for start. Also gathered lots of power and inspiration, so, here is a plan:

  • second filesystem contest, now I will test btrfs 0.13 and btrfs-unstable in addition to previous ext[234], reiser[34], jfs and xfs running for the first prizes in dbench, iozone, postmark, maildir performance bench and simple file creation micro-benchmark. Results will show need for the yet another local filesystem. Making bets?
  • fix two problems in distributed storage: there is a leak in mirror resync and unability to start a storage if config contains wrong network addresses.
  • rewrite core pohmelfs algorithms to make it not good, but really good. This change will make it first against CRFS and CacheFS :) POHMELFS is not where I want it to be right now.
  • fix HIFN driver bug.
Lots of stuff scheduled to be started tomorrow (actually today: it is about 3:30 AM here), but unlikely to happen - there is a plan to go climbing.

But nevertheless, stay tuned, lots of interesting stuff is coming!

/other :: Link / Comments (2)

Chris Mason wrote at 2008-03-20 16:37:

Thanks for giving btrfs a shot. For the random file operations (especially postmark), you'll want to:

mkfs.btrfs -l 4k -n 4k mount -o ssd

For raw throughput, you might need to mount btrfs -o nodatasum, especially on reads there is some checksumming tuning I need to do.

zbr wrote at 2008-03-20 18:09:

Yeah, I turned off data checksumming for all operations and will add ssd option to postmark test. All other optimizations include noatime, writeback for ext34, extents for ext4, and tweaks for xfs I got from your btrfs page. Also found, that 0.13 is still btrfs-unstable, so will get only that (my scripts are rather bad :)

Porting reiser4 to 2.6.24 requires quite a bit of work (besides changes to generic sync inode code), but it looks like it is very dead, namesys,com does not respond at all, its domain servers do not know such record.

Please solve this captcha to be allowed to post (need to reload in a minute): 2 * 0

Comments are closed for this story.