From: tytso@mit.edu
To: Paul Chavent <paul.chavent@fnac.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Constant access (write) time.
Date: Sat, 6 Mar 2010 18:13:27 -0500 [thread overview]
Message-ID: <20100306231327.GI6000@thunk.org> (raw)
In-Reply-To: <4B92D10D.8070805@fnac.net>
On Sat, Mar 06, 2010 at 11:02:53PM +0100, Paul Chavent wrote:
> Hello.
>
> I'm writing a real-time application that have to stream pictures to a SSD.
>
> The pictures are 640x480x1 pnm that are stored in one tar file. I
> have one picture every 100ms.
>
> The problem is that the access (write) time (from a userspace point
> of view) is not constant. I join you a piece of code that reproduce
> the problem.
What are you seeing/expecting? Here's what I'm getting with the X25-M
Intel SSD:
file size duration
diff min : 3666548
diff moy : 6639261
diff max : 9429924
101 iterations
major pagefaults : 0
minor pagefaults : 0
It's rarely if ever triggering your "suspect write" fprintf.
>
> This leads me to ask the following questions : the solution to this
> problem is
>
If you are seeing something seriously worse, you might want to test
what happens if you write to the SSD directly; it may be the answer is
(4) Buy a competently engineered SSD. :-)
- Ted
next prev parent reply other threads:[~2010-03-06 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 22:02 Constant access (write) time Paul Chavent
2010-03-06 23:13 ` tytso [this message]
2010-03-08 20:17 ` Paul Chavent
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=20100306231327.GI6000@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=paul.chavent@fnac.net \
/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;
as well as URLs for NNTP newsgroup(s).