🚀 go-pugleaf

In article <1992Oct6.160854.19152@cubetech.com> andrew@cubetech.com (Andrew Loewenstern) writes:
>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.
>
>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

    Simply put, that's an answer that is not an answer.  I should not have
    to put 256MB of memory in a machine to make it useable.  If a 16MB
    machine is not usable, THEN NEXT SHOULD NOT SELL A 16MB MACHINE.

    The NeXT has some *serious* problems with it's paging and file caching
    (and I've mailed bug_next with specific examples).  Adding so much
    memory to your machine that you are essentially completely defeating
    demand paged virtual memory is not a solution.  No matter how much
    memory you have, when the NeXT eventually pages something it usually
    pages the WRONG something and the machine hicups.

						-Matt

>--
>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

--

    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