From: Brad Frank <brad.frank@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Load spikes on intervals in qemu
Date: Tue, 17 Aug 2010 12:55:18 -0400 [thread overview]
Message-ID: <AANLkTikCN1RYaf_eYaKm13A9EmicbL92kOy9Cd5E5bLS@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
Yes, doing those things would be an alternative. But the bigger question is
why is fossil hitting the load like that while running in Qemu. And also,
another question is whether this would be happening on physical hardware as
well... Is there anything I can do to figure out why it is doing that, and
how to resolve it?
[-- Attachment #2: Type: text/html, Size: 321 bytes --]
next reply other threads:[~2010-08-17 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 16:55 Brad Frank [this message]
2010-08-17 18:29 ` Eric Van Hensbergen
2010-08-18 12:37 ` erik quanstrom
2010-08-18 15:12 ` Eric Van Hensbergen
2010-08-18 16:28 ` Venkatesh Srinivas
2010-08-19 0:40 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2010-08-19 2:19 Brad Frank
2010-08-17 13:50 Brad Frank
2010-08-17 14:07 ` Venkatesh Srinivas
2010-08-17 16:17 ` Eric Van Hensbergen
2010-08-18 12:42 ` erik quanstrom
2010-08-18 15:09 ` Eric Van Hensbergen
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=AANLkTikCN1RYaf_eYaKm13A9EmicbL92kOy9Cd5E5bLS@mail.gmail.com \
--to=brad.frank@gmail.com \
--cc=9fans@9fans.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).