Linked by Thom Holwerda on Wed 1st Apr 2009 13:15 UTC
Permalink for comment 356583
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2006-01-03
Several years back I was working for Tier 1 ISP provider. Doing some performance measurements across the cloud. Once in a lab I came across a couple of dozen of SGI stations, sitting on the shelf, doing nothing. Been told when company was looking for Unix stations to put on the cloud to measure traffic, somehow SGI convinced them to purchase their machines, on the basis of performance. What was the problem - software support. SGI implemention of Unix was sub par. Many standard interfaces didn't work properly. Many proprietory interfaces, poorly documented. Ended up getting Sparkstations.
I already had some programs I wrote and runing on Solaris. Out of curiosity I got one SGI station and tried to port the code on it. No luck. Many timer interfaces didn't even compile. Looked at documentation, realized SGI did lots of proprietory stuff. Gave up on the whole thing, decided not to waste my time.