From: Eric Dorman edorman@Tanya.ucsd.edu
Subject: [9fans] Ghost in the linker?
Date: Thu, 19 Feb 1998 15:16:02 -0800 [thread overview]
Message-ID: <19980219231602.SpHRLWLkDtRU1mZVXxUEaNHCfpOBgBf7nhQUO8XQ2ig@z> (raw)
forsyth wrote:
>
> >>8l gets to 40Mb during the link!
>
> that part is normal with ghostscript, as i recall.
> i had to relink the old version and i'm fairly sure i
> needed to do it on a 64mb cpu server.
I've compiled gs3.33 in 32mb on a pcdisk and it
pages pretty heavily. Compiling parts of libtiff
also page on my old 32mb config.
I've been wondering what the 'typical' installation
does (err, should do?) in cases where the cpuserver
starts to page heavily. It seems to me that w/o a
paging disk on the cpuserver (or terminals paging
heavily) there'll be an inordinate amount of traffic
on the network. Separate networks for cpu<>fs
activity could help but are annoying to manage.
I think one could just put gobs of memory in the
cpu and 'plenty' in the terminals and just take
the hit in the rare occasion memory runs out... it's
mostly pretty cheap these days, particularly compared
to cheap disks that provide really too much storage
for this task (plus hassle of having to maintain them).
Paging doesn't happen often, either.
OTOH I don't really know what the paging statistics
look like for a cpuserver with a large user base; maybe
a paging disk on the cpuserver is a win? (then again,
what is 'large'? 50? 1000? ).
Eric Dorman
edorman@tanya.ucsd.edu
next reply other threads:[~1998-02-19 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-19 23:16 Eric [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-20 20:47 Eric
1998-02-20 8:08 Nigel
1998-02-20 0:15 schwartz+9fans
1998-02-19 20:10 forsyth
1998-02-19 20:02 Eric
1998-02-19 8:57 Nigel
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=19980219231602.SpHRLWLkDtRU1mZVXxUEaNHCfpOBgBf7nhQUO8XQ2ig@z \
--to=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).