> > Could anyone consider fork a syncer process to sync data to disk ?
> > build a shared sync queue, when a daemon process want to do sync after
> > write() is called, just put a sync request to the queue. this can release
> > process from blocked on writing as soon as possible. multipile sync
> > request for one file can be merged when the request is been inserting to
> > the queue.
>
> I suggested this about a year ago. :)
>
> The problem is that you need that process to potentially open and close
> many files over and over.
>
> I still think it's somewhat of a good idea.
I like the idea too, but people want the transaction to return COMMIT
only after data has been fsync'ed so I don't see a big win.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
