Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: Babu Arunachalam who wrote (7521)	2/3/1998 3:02:00 PM
From: Chung Yang	Read Replies (1) \| Respond to of 64865

I am not an expert in computer networking, but in essence you are correct, but I think it is proabaly a little more simpler than that. As far as I know, the network people simply restrict user permission onto those machines and only allow it to be access via a priority-queue program. You would launch a job via that program which goes off and check to see which machine is free. (Actually, the program is more complicated than that, it does an analysis of load and try to balance network traffic vs. computing cycle ... etc. to maximize performance. Don't ask me how). Accessing files on a disk on another machine will be faster it is local to your subnet anyway. So I guess you are right. But I think in our job farm we have storage arrays, the capacity is much larger, the bandwidth is bigger, and the access is faster. Anyway, job farm is just a way to make a poor man's super-multiprocessor computer. I've seen PC used that way too, but it had to use UNIX operating system to do that. - Chung >>> I guess the term "Farm" is associated with creating subnets where your data on the ethernet doesn't go to the entire network but only within the subnet most of the time. Accessing files mounted on different machines is faster if the access is local to your subnet than having to be routed on the backbone and back?? Cheers, Babu <<<<