🚀 go-pugleaf

In article <BvnJ4A.pL.2@cs.cmu.edu> nash+@cs.cmu.edu (Richard Nash) writes:
>>In article <dillon.0oq2@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US  
>>(Matthew Dillon) writes:
>>> 
>>>     The main problem with 3.0 is in paging from disk, a faster processor
>>>     will not help at all in that area.
>>> 
>>>                                       -Matt
>>> 
>>> --
>>> 
>>>     Matthew Dillon            dillon@Overload.Berkeley.CA.US
>>>     1005 Apollo Way           uunet.uu.net!overload!dillon
>>>     Incline Village, NV. 89451        ham: KC6LVW (no mail drop)
>>>     USA                       Sandel-Avery Engineering (702)831-8000
>>
>>If only it were really that simple!
>>
>>Jim
>
>But it is true! Most of the perceived 'slowness' about next machines have to
>do with disk or network access. Even if the processor was infinitely fast,
>executing in zero time, the machine would look and feel almost as slow as
>it does today.
>
>Rich

GET MORE MEMORY!

You are using more memory than you have, that is why you are paging.

If you have a Turbo, try turning on the "swaptimizer" (see the swaptab
man page).  The swaptimizer compresses pages before they go out to
disk to reduce disk IO.  This works great (I use it on my 25mhz
machines) since you can't use the processor much during a page-fault
(since normally the windowserver causes the page-fault, and you must
wait to draw...), it makes sense.  It probably doesn't make sense on a
machine where you have a bunch of people logged in on ttys.


andrew
-- 
andrew@cubetech.com     | "We shall not cease from exploration
Andrew Loewenstern      |  And the end of our exploring
Cube Technologies, Inc. |  Will be to arrive where we started
                        |  And know the place for the first time." -T.S. Eliot