Slashdot Mirror


A Look at IRIX 6.5.17

XFS writes "OSNews got their hands on the latest version of IRIX, 6.5.17 (released in August), and they have published an interesting article about it and they explain why IRIX was and still is, one of the best workstation Unices out there. Especially when it comes to multimedia/GL performance. I hope SGI will do something with IRIX though, as they seem to have let it fall behind and be one of these great technologies that get lost through various corporate focus shifts..."

13 of 309 comments (clear)

  1. Re:Mmmmkay... by Anonymous Coward · · Score: 1, Informative

    Unstable????

    It _is_ better than windows, and if it was unstable for you, you have to look at your own skills...

    _YES_ I have managed many IRX Boxes for years, seems to me you breathed on one once...

  2. Fallacy of benchmarks by Anonymous Coward · · Score: 3, Informative

    I think it is pretty interesting that the benchmark that they used measured memory throughput of the graphics CPU, as opposed to, say, an actual workload-handling of the OS. In other words, this is a synthetic benchmark, versus a real-world benchmark. They say, "Look! We can do memory transfers really really fast!"

    Unfortunately, memory transfers are not the world when it comes to multiprocessor multimedia boxes. The overhead comes in when you're trying to synchronize a large number of threads/CPUs to do a large task. For example, an Oracle database.

    Sun has proven that it scales up the tree very well with large numbers of processors. But from my understanding, Linux is more efficient with a low processor count, and less and less efficient with more processors.

    I question its ability to do anything with a real workload. And I've even more suspicious because they use a benchmark I've never heard of to push its superiority on a single-aspect synthetic benchmark.

  3. Hmmmmm by IamTheRealMike · · Score: 5, Informative
    One of the most innovating things about the IRIX in the '90s were the vector icons it uses for its desktop and file/icon managers. IRIX had vector support by default in its desktop long before MacOSX ever existed.

    Not sure what this is implying, but it seems to be a surprisingly common misconception that MacOSX has vector based artwork. Not so. GNOME can do, and I think KDE3.1 can as well, via SVG. MacOS icons though are just bitmaps in a variety of sizes, with some scaling/blending algorithms applied.

    The SGI desktop is of course based on a heavily modified commercial X Server. And here I will stop for a second, get a big breath and say: 'wow'. I have never seen an X server being so fast, on a 5-year old machine (no matter if this is an SGI machine or not).

    I'd kind of expect this given that IRIX comes as a bundle with the hardware. When you choose the hardware as well as the software you can of course optimize the drivers a lot, so you will get good speeds out of it. XFree has to deal with a lot of different hardware, and the driver manufacturers are sometimes less than helpful. Probably worth remember that IRIX won't have some of the newer X extensions like XRender.

    1. Re:Hmmmmm by spitzak · · Score: 3, Informative
      NeXT (I programmed these things in the 1980's) certainly supported drawing using PostScript paths, but all "icons" were tiff files. In fact they added a special tag to tiff to represent their 2-bit gray screen.

      Until recently vector-based icons were way too slow. Except for the Irix ones, which were neceessarily quite simple. This simplicity did add to their appeal I think, though they never really put some good graphics designers on it.

      KDE and Gnome and OS/X all render the vectors into pixmaps and then blast the pixmaps on the screen. OS/X certainly supports pixmaps and all the icons that appear to be airbrushed are bitmaps. They scale quickly and nicely because they have them carefully rendered at several resolutions and use mipmapping (the same technique your fancy graphics card uses for textures when it is in it's highest-quality mode) to scale.

      Ignoring the drawing speed vector icons are much more efficient and take far less memory. In fact the earliest icons could be considered vector-based, they were drawn on vector screens by machines where 8K of memory was expensive.

    2. Re:Hmmmmm by Jamie+Zawinski · · Score: 2, Informative
      The SGI desktop is of course based on a heavily modified commercial X Server. And here I will stop for a second, get a big breath and say: 'wow'. I have never seen an X server being so fast, on a 5-year old machine (no matter if this is an SGI machine or not).

      I'd kind of expect this given that IRIX comes as a bundle with the hardware. When you choose the hardware as well as the software you can of course optimize the drivers a lot, so you will get good speeds out of it. XFree has to deal with a lot of different hardware, and the driver manufacturers are sometimes less than helpful.

      That's an interesting theory, but it is easily refuted with one word: Solaris.

      Sun has all those advantaged you mentioned, and their X server has consistently been the biggest piece of garbage to bear the name.

      The fact is, SGI's X server is just really, really good. Don't minimize their accomplishment by assigning credit to captive hardware: it's really high quality software, plain and simple. In 8+ years of using it, I saw an Xlib client bring down the server maybe twice. That's pretty much an hourly occurence with a Sun server, until you learn what not to do.

      Of course, some of the credit goes to SGI's graphics hardware, which has always been great.

      For example, it is still impossible to find a combination of hardware and software for Linux that will let you mix visuals of multiple depths on the same screen (e.g., having one window be 24 bit TrueColor, and two others be 8-bit PseudoColor with different simultaniously installed colormaps) while still having acceleration turned on. (I need to do this kind of thing to properly debug various xscreensaver configurations.)

      Since I switched from my SGI O2 to a Linux machine, I've been solving this problem by having two monitors, one running in 24 bit and one in 8 bit, and it's hard enough even getting that to work without crashing at random every couple of days. Unless I turn off acceleration, which makes my dual-1600MHz vintage-2002 Linux box do graphics at half the speed as my 200MHz vintage-1996 SGI O2.

      SGI's X server rocks. I miss it dearly.

  4. You're an idiot by Anonymous Coward · · Score: 2, Informative

    IRIX could gain a huge boost in popularity if people could "try it at home" on cheap x86 hardware

    So you think that SGI should spend huge amounts of money and development time porting IRIX to x86, and then give it away free, simply so that you can "try it out at home"?

    Are you aware of the fact that IRIX does not run on x86 hardware? Are you aware of the fact that SGI will be moving to Linux on IA-64 in the future, rather than attempting to port IRIX to the IA-64? Do you, in fact, have any idea of how much work it would be to port IRIX to anything other than MIPS?

    No? Didn't think so.

  5. Re:What about... by duffbeer703 · · Score: 4, Informative

    That's funny.

    AIX has more (and growing) marketshare than Irix has had in years. The Power4 and Power5 chip is attracting alot of business away from Sun.

    SGI has been obsolete since 1996. A $2,500 Dell Workstation can do as much as a $25,000 SGI workstation.

    Wake up McFly! It's 2002 calling!

    --
    Conformity is the jailer of freedom and enemy of growth. -JFK
  6. Irix is painful and unpleasant by Montressor · · Score: 5, Informative

    IRIX might have enterprise-level performance, but it suffers enormously in the usability department. I work in a lab where IRIX is standard, because 64-bit memory addressing and extreme graphics performance using ImageVision is a must. However, I keep running into issues with the development tools. Most impotantly, SGI's cc (c compiler) is slow and hard to customize flags on, especially for debugging. Furthermore, frequently, if my program commits a memory fault, it receives a SIGKILL rather than a segfault which makes it very difficult to debug (this usually happens if the malloc pool gets corrupted or while using ImageVision).

    The ImageVision library (an OpenGL-based image processing system) hsa great performance and features. However, it refuses to link with programs not built with cc (thus, no gcc!). Furthermore, programs that seem to follow spec mysteriously die with a SIGKILL during deallocation. I certainly realise that I might be doing something wrong in the way I call the library, but it does not provide any error
    message, exception, or fault.

    Finally, IRIX standard header files are a colossal mess and almost impossible to use. Standard C and C++ objects are casually redefined throughout the header structure.

  7. Re:What about... by gfxguy · · Score: 2, Informative
    Isn't it more a case of gfx/animator studios are buying loads of Intel boxen and slapping Linux on them rather than buying SGI kit (expensive kit I might add), and is working out to be cheaper for the studios?
    Yes and no. We (sadly) replaced a number of SGI animator computers with Windows 2000k. We tried Linux for the render farm, but at the time Maya did not render, pixel per pixel, the exact same images that Windows would render, and that wasn't acceptable. I don't know what the status of Maya on Linux is now.

    The speed/cost ratio is much better with PCs, even though you need a fairly high end PC in order to run demanding 3D applications.

    I've been arguing in my department that the cost savings don't outweigh the drawbacks of using Windows with demanding applications: blue screens, flakey "drive mapping", license servers that don't work as expected...

    PCs are great for render farms, but I still think the interactive use for the high end 3D applications is better done, and more cost effective, on SGIs. It's not the PC, it's the OS...

    On a side note, we had a recent visit from SoftImage (no longer an MS subsidiary) demonstrating XSI (very cool but expensive application). The person who was demonstrating said they had up to 20% speed improvements on Linux over Windows 2000, although there are certain features in the Windows version not available on the Linux version.

    We use Maya, though, and while Maya is available for Linux, the other tools we use (many Adobe tools, for example) are not. Our render boxes are Windows, for consistency.

    We still use SGI's for a variety of applications that, as the article pointed out, a five year old SGI is still better than a brand new PC. Flame/Inferno compositing, for one, and some real time 3D applications. Also cell animation ink and paint. There are some things the SGI can do as far as video I/O that PCs simply can't do at all. PCs are certainly coming close, though.

    --
    Stupid sexy Flanders.
  8. Re:Mmmmkay... by Anonymous Coward · · Score: 1, Informative

    That might be the most unintelligent post ever made on Slashdot. What a great advertising campaign that would be for a campaign. Please don't use our product if you are not a certified expert in using our product. I have found it to be just the opposite. It is hard to crash a box from just using it (except maybe Windows 9X) but it is easy to crash when you think you are an expert and start twiddling where your thumbs don't belong.

  9. Re:Why is SGI not switching to FreeBSD ? by fgodfrey · · Score: 4, Informative
    How on earth did this comment get moderated "insightful"?!?! I'm not really sure where to start here:


    crash-resistant, high-performance file system. Ever heard of "XFS"??? It's journaled and has been around almost longer than the FreeBSD project.


    First multithreaded kernel: Um.... Right... Multithreaded kernels have been around for probably a decade if not more. FreeBSD is hardly the first. Irix has had kernel threads for ages. The first reference I can find to them is in '95 (and I suspect they have been around longer than that) when FreeBSD didn't even run on multiprocessor systems.


    First "compact" kernel: What is a "compact" kernel? The FreeBSD kernel is a monolithic BSD kernel. Irix is a monolithic System V kernel. Even Linux is a monolithic kernel (of Linus + other's design). Microkernels haven't lived up to their initial hype (though MacOS X uses one), but neither they nor monolithic kernels are "obsolete".


    Now don't get me wrong, FreeBSD is a great OS. I have run it in the past and regularly use it. But it doesn't run on 1024 processors, have multiple tens of terabytes of storage in a single filesystem, and manage a terabyte of RAM. It's not designed for that. Irix is.

    --
    Go Badgers! -- #include "std/disclaimer.h"
  10. IRIX is SVR4, not BSD based. by cant_get_a_good_nick · · Score: 3, Informative

    Minor quibble, but it mentions it's different than Linux because it's UCB BSD based. It's not (well, it is up to teh point that SVR4 took a lot of BSDisms) but it's SVR4 machine. Linux distros generally take a bit from classic BSD, a bit from SVR4, and a bit of whatevehell else they want, so they're all a bit different.

  11. I just got an Octane by user32.ExitWindowsEx · · Score: 2, Informative

    This is weird. My Octane arrived the day this article was posted. I personally like 4dwm. Clean and simple.

    --
    "Evil will always triumph because good is dumb." -- Dark Helmet