Felix Palmen wrote:
>* Rick Macklem <rmack...@uoguelph.ca> [20211009 15:35]:
>> Felix Palmen wrote:
>> Assuming your NFS performance is acceptable for other things and it
>> is only this log file that is a problem, then I doubt there is much you
>> can do to improve it.
>
>Yes, that's the only problem I found so far…
Another thing you could try is turning off synchronous writing at the NFS
server.
# sysctl vfs.nfsd.async=1
and "sync=disabled" for ZFS if it is a ZFS file system that is exported.
However, BE FORWARNED:
Doing so violates the NFS RFCs because it can result is data loss/corrupted
files
that are being written when the NFS server crashes/reboots.
Only do it if the data being written to the NFS server is not particularly
important stuff.
rick
> --> Append (as in O_APPEND opens) are a poor case for NFS, since there
> is no append write in NFS. To approximate append write, it must flush
> all dirty data to the server, do a Getattr to find out the file's
> current
> size and then do the write (over and over and over again).
Ok, thanks for the insight here! So maybe, I could have a look at
poudriere's code? If I understand you correctly, keeping the file open
and just issuing more write() calls wouldn't trigger that problem?
> You could try the "nocto" mount option, which might help, if the log file
> is being re-opened many times, but I doubt it will help.
Well, I take any suggestion, so will try that as well and report back,
thanks again!
Side note, please don't CC/To me, I'm subscribed the list ;)
--
Dipl.-Inform. Felix Palmen <fe...@palmen-it.de> ,.//..........
{web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de
{pgp public key} http://palmen-it.de/pub.txt // """""""""""
{pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A
