From: Jeff Sickel <jas@corpus-callosum.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Interesting behavior...
Date: Fri, 5 Mar 2004 13:37:47 -0600 [thread overview]
Message-ID: <94EAB50A-6EDC-11D8-8A93-003065E1714E@corpus-callosum.com> (raw)
In-Reply-To: <e3704ae32182.e32182e3704a@cwru.edu>
I had a similar experience yesterday when doing
bunzip2 -c backup.tbz | tar xT
onto a fossil file system. I'd originally archived my files from a kfs
system and didn't have the same load issues.
Now aside from bunzip2 putting in a significant load, fossil also
contributed. And of course stats not only showed load at 100%, course
context switching like mad.
jas
next prev parent reply other threads:[~2004-03-05 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 15:59 Noah Evans
2004-03-05 19:37 ` Jeff Sickel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 15:50 plan9fans
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=94EAB50A-6EDC-11D8-8A93-003065E1714E@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@cse.psu.edu \
/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).