Hello!
On Mon, Jan 16, 2017 at 07:10:41AM -0500, nicktgr15 wrote:
> Thanks for the useful information Maxim!
>
> We ended up using strace to monitor the system calls and it looks like that
> with our current setup (i.e. default buffer size) the record length is 65536
> bytes.
>
> read(17, "\35
When a call to rename(2) returns -1 and in errno the value es EXDEV, it
means the system file doesn't support the rename feature, so the
application is supposed to be able to solve this creating a file in the new
filesystem and deleting the old file. This is something that I read
recently about auf
Thanks for the useful information Maxim!
We ended up using strace to monitor the system calls and it looks like that
with our current setup (i.e. default buffer size) the record length is 65536
bytes.
read(17, "\355\247=^\256\36\361\235~\356z"..., 65536) = 65536
write(18, "\355\247=^\256\36\361\
Hello!
On Thu, Jan 12, 2017 at 12:18:28PM +, Nikolaos Tsipas wrote:
> Hello,
>
> We're load testing nginx focusing on disk IO performance and we're trying
> to understand what's the record length used during caching operations. The
> reason why we'd like to know the utilised record length is
Hello,
We're load testing nginx focusing on disk IO performance and we're trying
to understand what's the record length used during caching operations. The
reason why we'd like to know the utilised record length is that we could
then use similar settings during our SSDs load tests.
We had a look
