Minimum Unixware harware (WAS: Re: Unixware FAQ?)

Minimum Unixware harware (WAS: Re: Unixware FAQ?)

Post by World I » Thu, 21 Apr 1994 13:19:00




> ...
>However, I am actually running UnixWare (1.1 PE at the moment) on a 486DX/25
>with 10MB ram. And yes, the performance is not bad at all. The reason for this
>is that the computer is a MCA machine with a 1640 controller and a fast disk.

>So, while it swaps like mad, it doesn't really matter, because the swapping
>is really fast.
>The machine does really well as a UnixWare machine, since its a strange
>NCR machine that doesn't run Windows properly, and isn't very fast.
>But Unixware can use the bus, and seems to be stable. (I'm slowly getting
>pretty impressed with UW, actually).
>>        Jim is also right about NT... It's positively sluggish running
>>even on a 486/33 with 16 MB.

>No, I think it runs fine on 16MB. If you don't load any applications.

I think it's the desktop. I experimenting with 1.1 on a 33meg 486SX with 8MB
to use as my internet server and it runs fine when no one's logged in to it.
If I log in and display the desktop remotely it's still a _lot_ faster then
running on UnixWare console itself.

BTW: Displaying the desktop on Solaris x86 gives you a NICE LOOKING and FAST
desktop. But it: takes over the background, destroys the mutliclick timeout
value (so double-clicking openwindows icons doesn't work,) and it wipes out
the command tool window that you rlogin'ed in on AND takes out the console
window (which you can't get back) when you shut down the UnixWare desktop.

 - Ed.
--
 -------------------------------------------------------------------
  Ed Taychert   | Disclaimer:  I pay for the machine, I pay for the

 
 
 

Minimum Unixware harware (WAS: Re: Unixware FAQ?)

Post by Steve Wa » Sat, 23 Apr 1994 01:20:31



>I think it's the desktop. I experimenting with 1.1 on a 33meg 486SX with 8MB
>to use as my internet server and it runs fine when no one's logged in to it.
>If I log in and display the desktop remotely it's still a _lot_ faster then
>running on UnixWare console itself.

To be more correct, the problem is the USL X server.  To get better performance
under X in UW 1.1, the scheduling class of the X server was changed from
timeshare to fixed.  This has the effect of giving the X server more CPU than
before, with the side effect of stealing cycles from other processes.

Your other problem is that you don't have enough RAM.  To use X you should
really have 12MB or better 16MB of RAM.

Steve
--
Steve Ward, Jr., System operator
School of Engineering, University of Portland
Portland OR