Article View: comp.sys.next.hardware
Article #848Re: Nitro
From: andrew
Date: Sun, 11 Oct 1992 09:47
Date: Sun, 11 Oct 1992 09:47
50 lines
3009 bytes
3009 bytes
In article <dillon.0ox5@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
>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.
It depends on what you call usuable. I used a 16mb color 3.0 machine
for about a week while waiting for some more memory to come in. It
was plenty usuable and I abuse the hell out of my machines. I
certainly wouldn't want to print to the Iris on it (now you know why I
have a 600mb swap drive... :-), but it was fine. For the vast
majority of users it would be more than adequate. What I'm getting at
is that a usuable configuration is relative to how the user uses it.
If you find that the performance is unacceptable due to paging, then I
would reccommend getting more memory. If you run out of memory, you
page. It doesn't matter what operatiny system you are on. If you
can't deal with that, either use less memory, or get more RAM.
NeXT shouldn't sell 8 and 12mb RAM configurations; and they don't
anymore.
> 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.
Like what?? Mach has a *killer* VM system.
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
Technical Details
Message-ID:
<1992Oct11.094702.3509@cubetech.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!kithrup!stanford.edu!ames!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!rpi!psinntp!psinntp!cubetech.com!imladris!andrewReferences:
<BvnJ4A.pL.2@cs.cmu.edu> <1992Oct6.160854.19152@cubetech.com> <dillon.0ox5@overload.Berkeley.CA.US>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.hardware Path: arc1-ca.pugleaf.net!sparky!uunet!kithrup!stanford.edu!ames!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!rpi!psinntp!psinntp!cubetech.com!imladris!andrew From: andrew@cubetech.com Subject: Re: Nitro Message-ID: <1992Oct11.094702.3509@cubetech.com> Organization: Cube Technologies, Inc. References: <BvnJ4A.pL.2@cs.cmu.edu> <1992Oct6.160854.19152@cubetech.com> <dillon.0ox5@overload.Berkeley.CA.US> Date: Sun, 11 Oct 1992 09:47:02 GMT Lines: 50