Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're probably right. Do you think it's cache at the VM level before writing to disk. Would writing more data out help at all?

  $ dd bs=1M count=40960 if=/dev/zero of=test conv=fdatasync
  40960+0 records in
  40960+0 records out
  42949672960 bytes (43 GB) copied, 48.455 s, 886 MB/s


The VM should always pass through proper fsync() semantics, so probably not that layer. But they mention battery-backed raid controllers, and it would be appropriate for fsync() to complete after the data has gotten into battery-backed memory, but before it gets to the actual disks.

(Okay Linode, you've finally done it. I'll get rid of my oddball $30/mo plan sometime soon. That extra $10 used to get me a necessary 180MB of extra RAM!)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: