From: Michael Weinrich <micxer@micxer.de>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Testing write master and multiple read clients on NFS share
Date: Wed, 20 May 2015 13:51:08 +0200 [thread overview]
Message-ID: <555C752C.20806@micxer.de> (raw)
In-Reply-To: <CALjAwxjze_LWfTgp=PTn3uOfYwF_cUq3uDZoB1Q8QffCwpdojQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Yeah, well, I needed a process that writes to the same files the others
are reading from to somehow simulate expiring local caches (and to see,
if NFS handles that the right way). And yes, it took me quite some time
to dig through most of the options to tailor the tests to my needs
But I'm also glad to hear, that it doesn't look completely wrong for a
first try :-)
Am 20.05.2015 um 11:03 schrieb Sitsofe Wheeler:
> On 17 May 2015 at 21:55, Michael Weinrich <micxer@micxer.de> wrote:
>> Thanks for the hint. I also found another mistake in limiting the reads and
>> writes where I only wanted to limit the writes and have the reads as fast as
>> possible. But in general this is a viable approach to my problem?
> I can't say for sure whether it models your workload (your example
> made use of options I had to look up!) but it does look like an
> interesting approach...
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4213 bytes --]
next prev parent reply other threads:[~2015-05-20 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 22:09 Testing write master and multiple read clients on NFS share Michael Weinrich
2015-05-16 11:46 ` Sitsofe Wheeler
2015-05-17 20:55 ` Michael Weinrich
2015-05-20 9:03 ` Sitsofe Wheeler
2015-05-20 11:51 ` Michael Weinrich [this message]
2015-05-22 0:06 ` danielabuggie .
2015-05-24 1:15 ` Jens Axboe
2015-05-24 20:50 ` Michael Weinrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555C752C.20806@micxer.de \
--to=micxer@micxer.de \
--cc=fio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox