Which gets into the client and server question.

The server should be grinding data, not generating graphics. Graphics
are presentation and should be the responsiblity of the workstation
(client). digesting the data that is the basis of the graphics is the
server's business, which is going to require more I/O handling capacity,
which a mainframe is capable of. 

100 virtural machines to manage and grind the data that feeds 100 real
workstations to draw pretty pictures from the data.

-----Original Message-----
From: Alan Cox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 2:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Whither consolidation and what then?


On Maw, 2003-07-29 at 19:10, Fargusson.Alan wrote:
> At one time I did a lot of work with Unix, and I never had any
problems with
> multiple processes corrupting the memory of other processes.  Have
there
> been some bugs introduced into Unix recently?

Not that I've noticed. Multiuser has gone out of fashion

 19:31:25  up 10 days, 21:32, 53 users,  load average: 0.10, 0.07, 0.05

but it still works (reboot from upgrading the kernel)


Spreading load across a lot of PC's gets you colossal amounts of CPU
power but at management cost. The big trick is becoming solving that
management problem - replicated system filestores, capacity management,
session dump/restore etc.

You can run 100 sessions on a 390 but I don't think you get the
equivalent of 300Ghz of CPU power.


Confidentiality Warning:  This e-mail contains information intended only for the use 
of the individual or entity named above.  If the reader of this e-mail is not the 
intended recipient or the employee or agent responsible for delivering it to the 
intended recipient, any dissemination, publication or copying of this e-mail is 
strictly prohibited. The sender does not accept any responsibility for any loss, 
disruption or damage to your data or computer system that may occur while using data 
contained in, or transmitted with, this e-mail.   If you have received this e-mail in 
error, please immediately notify us by return e-mail.  Thank you.

Reply via email to