From: Stewart Smith <stewart@flamingspork.com>
To: Dave Chinner <david@fromorbit.com>, Jason Newton <nevion@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: followup on benchmarks of an xfs embedded system (without rt section)
Date: Tue, 31 Jul 2012 11:06:00 +1000 [thread overview]
Message-ID: <87r4rssps7.fsf@flamingspork.com> (raw)
In-Reply-To: <20120730221105.GK2877@dastard>
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
Dave Chinner <david@fromorbit.com> writes:
> On Fri, Jul 27, 2012 at 03:35:40AM -0700, Jason Newton wrote:
>> I've attached my benchmark program but I use alot of boost c++ with a
>> little internal set of libraries... so you can see what I"m doing but it
>> likely won't compile for you. I'll also mention that boost is a very low
>> overhead (if any) over all the normal system calls one would use (verified
>> by reading sourcecode in use).
>
> I'd suggest rewriting it so we can compile and run it. If I can
> reproduce the problem, I can at least understand where the latency
> is coming from.
The boost::chrono usage is the weirdest one that'll likely cause
issues. Should be replaced with boost::posix_time instead (it's been
around a lot longer)... otherwise it's just having to install all the
boost headers I think (boost is basically 99.9% implemented in header
files and templates)
--
Stewart Smith
[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-07-31 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 10:35 followup on benchmarks of an xfs embedded system (without rt section) Jason Newton
2012-07-30 22:11 ` Dave Chinner
2012-07-31 1:06 ` Stewart Smith [this message]
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=87r4rssps7.fsf@flamingspork.com \
--to=stewart@flamingspork.com \
--cc=david@fromorbit.com \
--cc=nevion@gmail.com \
--cc=xfs@oss.sgi.com \
/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.