9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 3e mpg123 plays on off on off on off on 4e
Date: Fri,  3 May 2002 16:58:15 +0200	[thread overview]
Message-ID: <200205031458.g43EwFD02096@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 03 May 2002 10:42:22 -0400." <fe8192c80287a783d86450275fcdda04@plan9.bell-labs.com>

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

> I believe you that the 3e installation worked fine.
> Much has changed, though.  One thing you might try
> is boot your 3e installation (if you still have it)
> but use the 4e u9fs (which speaks both protocols).
>
> Maybe I managed to make u9fs even slower than it
> was, although I expect it should be about the same.
>
> What if you just time cp?  Can you see a difference
> between fs and u9fs?  Between 3e and 4e u9fs?

I just tried your last suggestion, repeating the same
iostats experiment with 3 u9fs.
(see last part of attachment)

(By the way: for maintenance they will shut down main
 servers here in about 20 minutes, for several hours;
 next week I'm away and may or may not have email access)

Axel.


[-- Attachment #2.1: Type: text/plain, Size: 333 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: text/plain ; name="mp3.iostats"; charset=us-ascii
	Content-Description: mp3.iostats
	Content-Disposition: attachment; filename="mp3.iostats"

[-- Attachment #2.2: mp3.iostats.suspect --]
[-- Type: application/octet-stream, Size: 2957 bytes --]

cpu% iostats cat  /n/zamenhof/tmp/a.mp3 > /dev/null

read      4569410 bytes, 380.1597 Kb/sec
write     4558730 bytes, 46373.32 Kb/sec
protocol  9167243 bytes, 730.8666 Kb/sec
rpc       1143 count

Message    Count   Low  High  Time Averg          in      out
version        1     0     0     0     0 ms       19       19 bytes
attach         1     2     2     2     2 ms       25       20 bytes
walk           9     1   197   351    39 ms      261      332 bytes
open           5     0    35    39     7 ms       60      120 bytes
read         562     2   145 11738    20 ms    12926  4575592 bytes
write        557     0     1    96     0 ms  4571541     6127 bytes
clunk          8     0    19    23     2 ms       88       56 bytes

Opens    Reads  (bytes)   Writes  (bytes) File
    1      558  4558730        0        0 /n/zamenhof/tmp/a.mp3
    1        0        0      557  4558730 (stdout)
    1        4    10680        0        0 /bin/cat
cpu%  iostats cat /tmp/a.mp3 > /dev/null

read      4569410 bytes, 760.5784 Kb/sec
write     4558730 bytes, 44968.08 Kb/sec
protocol  9167204 bytes, 1384.312 Kb/sec
rpc       1143 count

Message    Count   Low  High  Time Averg          in      out
version        1     0     0     0     0 ms       19       19 bytes
attach         1     2     2     2     2 ms       25       20 bytes
walk           9     1   436   488    54 ms      248      306 bytes
open           5     0     4     9     1 ms       60      120 bytes
read         562     1    16  5867    10 ms    12926  4575592 bytes
write        557     0     4    99     0 ms  4571541     6127 bytes
clunk          8     0     1     2     0 ms       88       56 bytes

Opens    Reads  (bytes)   Writes  (bytes) File
    1      558  4558730        0        0 /tmp/a.mp3
    1        0        0      557  4558730 (stdout)
    1        4    10680        0        0 /bin/cat
cpu%
cpu% srvold9p -c -F -m /n/kremvax -p kremvax -n tcp!zamenhof!9fs
cpu% iostats cat  /n/kremvax/tmp/a.mp3 > /dev/null

read      4569410 bytes, 1501.957 Kb/sec
write     4558730 bytes, 42398.5 Kb/sec
protocol  9167190 bytes, 2840.207 Kb/sec
rpc       1143 count

Message    Count   Low  High  Time Averg          in      out
version        1     1     1     1     1 ms       19       19 bytes
attach         1     3     3     3     3 ms       25       20 bytes
walk           9     1    26    54     6 ms      246      306 bytes
open           5     1     8    14     2 ms       60      120 bytes
read         562     1    13  2971     5 ms    12926  4575592 bytes
write        557     0     1   105     0 ms  4571541     6127 bytes
clunk          8     0     2     4     0 ms       88       56 bytes

Opens    Reads  (bytes)   Writes  (bytes) File
    1      558  4558730        0        0 /n/kremvax/tmp/a.mp3
    1        0        0      557  4558730 (stdout)
    1        4    10680        0        0 /bin/cat

  reply	other threads:[~2002-05-03 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 14:42 Russ Cox
2002-05-03 14:58 ` Axel Belinfante [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-03 14:58 Russ Cox
2002-05-03 15:13 ` Axel Belinfante
2002-05-02 21:58 Russ Cox
2002-05-03  8:45 ` Don
2002-05-03 10:12   ` Axel Belinfante
2002-05-03 14:23     ` Axel Belinfante
2002-05-02 21:53 Axel Belinfante

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=200205031458.g43EwFD02096@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).