[stgt] Performance Issue
ronniesahlberg at gmail.com
Wed Jan 18 02:06:54 CET 2012
You probably shouldnt remove fsync() completely,
but make sure that you have fsync() called at least from the
That would mean that if the backup finished successfully, that final
write is followed by a single fsync() call so that if
WRITE, WRITE, ... WRITEFILEMARK has completed successfully you know
the data is safe on stable storage.
But you dont pay the price for fsync() on each data write.
On Fri, Dec 9, 2011 at 7:33 AM, Gabriele <gabriele.mailing at rvmgroup.it> wrote:
> After removing fsync(fd), I tried to wrote and read some tape images: all
> went good.
> I think it would be useful to add an option to tgtd or to the device created
> that allows skipping fsync(fd), remembering that is a performance goodie,
> but not so safe ...
> To unsubscribe from this list: send the line "unsubscribe stgt" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the stgt