From: David Chatterton <chatz@melbourne.sgi.com>
To: nagesh kollu <nagesh_20k@yahoo.co.in>
Cc: linux-xfs@oss.sgi.com
Subject: Re: about performace
Date: Fri, 29 Sep 2006 00:12:20 +1000 [thread overview]
Message-ID: <451BD844.4000509@melbourne.sgi.com> (raw)
In-Reply-To: <20060928065113.70796.qmail@web8511.mail.in.yahoo.com>
In general (no experience or suggestions for ARM processors), for video streaming:
- preallocate space for the files when writing, see xfsctl(3) and XFS_IOC_RESVSP
- use direct I/O, the larger the better. ie a MB or more at a time,
but at least ensure the direct I/O requests are aligned on page or
filesystem block boundaries, whichever is larger
- use asynchronous I/O or multiple threads to keep the disks busy
David
nagesh kollu wrote:
> hi,,
> i'm new to xfs ..i want to know the performance details of xfs..
> how much time it will take to write /read ...can anyone done this on ARM processor...the block size is 2^n only in xfs ..but for video streaming the incoming packet is 188 bytes .the sector size is 512 ...so the i/o buffer size is 188*512 ...how can we do this in xfs....cany anyone send the xfs performance details..
>
>
> thanx!
> nagesh.k
>
>
> ---------------------------------
> Find out what India is talking about on - Yahoo! Answers India
> Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
>
> [[HTML alternate version deleted]]
>
--
David Chatterton
XFS Engineering Manager
SGI Australia
next prev parent reply other threads:[~2006-09-28 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 6:51 about performace nagesh kollu
2006-09-28 14:12 ` David Chatterton [this message]
2006-09-28 15:16 ` Eric Sandeen
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=451BD844.4000509@melbourne.sgi.com \
--to=chatz@melbourne.sgi.com \
--cc=linux-xfs@oss.sgi.com \
--cc=nagesh_20k@yahoo.co.in \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.