Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Is Mac OS X Slow?

Posted by Cliff on Thu Nov 07, 2002 04:40 PM
from the it's-not-slow-for-me dept.
Junks Jerzey asks: "Every time there's a mention of Mac OS X on Slashdot, there's a flurry of responses about how unbearably slow Mac OS X is. To anyone who has done software development under both Mac OS X and Windows or Linux, is there any truth to this or is it simply a knee-jerk reaction from non-Mac users who see low numbers like 800MHz. I'm talking about average priced Macs here, like the LCD iMac line, not the dual 1.25GHz machines that sell for $4500+." Having the fortune of using a Titanium Powerbook for over a month, I don't find Mac OS X that slow at all, however, there are some things that do take a little longer than I am used to, but I think these things are application-specific. For those Mac OS X users out there, have you noticed operations that seemed slower using Mac OS X compared to similar operations on other operating systems?
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by spoot (104183) on Thursday November 07 2002, @04:42PM (#4619971) Homepage
    but this damn thing is to slowwwwwwww
    • by sdjunky (586961) on Thursday November 07 2002, @04:48PM (#4620046)
      Your sentence.
      "but this damn thing is to slowwwwwwww"
      suggested grammar and spelling.
      "but this damn thing is too slow"

      GRAMMAR AND SPELLING CHECK COMPLETE: 15 minutes 23 seconds 67 ms
        • by Polo (30659) on Thursday November 07 2002, @10:24PM (#4622659) Homepage
          Actually, A mac would just have a blue bar with
          "About 15 minutes"
          under it. ;)

          (of course, it would wildly swing to 45 minutes, 12 minutes, 22 minutes and so forth throughout)
      • Re:Answer to title. (Score:5, Informative)

        by Jezza (39441) on Thursday November 07 2002, @05:54PM (#4620882)
        Mac OS X isn't actually slow but has a lot of technologies that have got a bad rap (though they didn't always deserve them).

        Mac OS X is based on a Microkernel - now everyone agrees these are slow, right? Well, sure I can see where that's coming from - but Apple have gone to great lengths to make this as fast as possible without losing the benefits. So the Kernel isn't actually slow, it compares well with other BSDs and Linux.

        The Mac is only 800MHz(ish) for low end machines so it must be slow? This is the classic "MHz Myth" the G4 has a short pipeline (a good thing) and executes over 90% of it's instructions in 1 cycle or less (the modern definition of RISC, TRIVIA: the old definition was implements less the 100 instructions). And then there's the amazing AltiVec (which Apple call the "Velocity Engine", if you see these terms they refer to the same thing). Macs have blistering real math performance (the G3 iBook doesn't have the AltiVec).

        Macs are based on Objective-C - that's REALLY slow. Well sure if you just implemented Objective-C without optimisations then it would be slow, but NeXT (them that did the Objective-C implementation) didn't do that. They added a method lookup cache which speeds things up a great deal, and IMPs that can be used in tight loops to gain extra zip (healh warning, IMPs are not ususally needed and can cause stunning bugs if you're not careful with them - unless you have a large tight loop that REALLY needs speeding up - don't bother with IMPs). The use of allocation zones can also speed up the VM system a great deal (these aren't as troublesome as IMPs can be, but again aren't as often needed as you might think). The Kits make heavy use of these tricks so they are pretty fast.

        Quartz has lots of tricks to make it fast, and now all current Macs can make use of Quartz Extreem (uses the compositor on the GPU to dramatically speed up the whole windowing system).

        So no Macs aren't slow. Apple's site includes server stats and they are very impressive too.

        But the implementation details aren't widely understood so a lot of people's initial reaction is "Oh that's gotta be slow" - it really isn't.
        • Re:Answer to title. (Score:5, Informative)

          by be-fan (61476) on Thursday November 07 2002, @07:43PM (#4621704)
          Actually, the kernel is slow. In lmbench (which measures the speed of basic UNIX kernel operations) OS X is half the speed of Linux. And the Velocity engine would be great...if the G4 had enough front side bus bandwidth to actually feed it. The AltiVec units themselves are very high quality, but because the average P4 has 3x the memory bandwidth (and streaming SIMD operations are *very* memory bandwidth dependent) it can't shine in the current G4.
          • by Halo1 (136547) <jonas,maebe&elis,ugent,be> on Friday November 08 2002, @04:22AM (#4623923) Homepage
            The reason the kernel is slower than under Linux, is mainy that the Mac OS X kernel is designed to deliver the best overall performance, not the best optimal performance. This means that when you put a machine under heavy load, the speed of those kernel operations under Linux takes a sharp nosedive (way below the Mac OS X numbers), while those of Mac OS X stay more or less the same. This is quite important for semi-realtime applications such as audio/midi processing, digital video etc.

            The fact that it is based on a microkernel doesn't matter, because the Mac OS X kernel is not a microkernel anymore. The whole kernel runs in one address space (so no message passing between different kernel components), just like in Linux. They still kept the different parts of the kernel more or less distinct in the source, but this is simply for easier maintenance.
                  • Re:Answer to title. (Score:5, Informative)

                    by lemkebeth (568887) on Friday November 08 2002, @12:58AM (#4623393)

                    :rolls eyes:

                    How did this clueless post get modded up?

                    Anyway you said:

                    Yes it is old code. Mach 2.x, mostly 4.4 BSD.

                    No it isn't that version of Mach. Apple switched versions of Mach (3.0 OSF I think it was). The BSD code is much newer than what NeXT used.

                    You also wrote:

                    10.1.5. Not 10.2, as mac-heads say when I point it out, but if you'd read the changelogs, you'd realize that the GUI was the focus of 10.2 development, not the kernel.

                    They did make significant changes to the kernel. I'm on the Darwin list.

                    Finally you wrote:

                    Doesn't change the fact that the layering involves a layer of redundency and abstraction that hurts performance.

                    Yes it does. having the BSD kernel in the same file, the same address space, etc, DOES increase performance.

                    I will say this again, so it gets through your Linux biased skull, that the version of Mach is not 2.5 (the version NeXT used). Hell it isn't even the CMU version anymore.

        • by autopr0n (534291) on Thursday November 07 2002, @07:47PM (#4621731) Homepage Journal
          They wanted to know if MacOS seemed slow to the users on mid-range macs. Not if it would be 'theoretically fast' based on the technology.

          Basically what they really need to know is 'interface latency'. How long between when you click and when something happens. Things like Vector engines are not going to help this.

          While the P4/Athlon and (I assume) G4 can all run more then one instruction at once (not just one) that's irrelevant, what is being asked here is if the OS is slow for the hardware it's running on. Win95 would be blazing fast on a p3-500 with 128 megs of ram, but XP would run like a hog on the same machine.

          Since I seriously doubt anyone has any kind of actual measurements this is basically going to be nothing more then a page-view generating flamewar on slashdot.
        • I love this technical discussion of why the Mac is considered to be slow but actually isn't. The asker is probably not as interested in a detailed technical minutae as the user experience.

          I'm a professional software developer that had to port a large body of code from Windows to Mac. I've also done a signifigant amount of work on *nixes. The Finder interface in 10.0 and 10.1 is unbearably slow. I haven't had enough experience with 10.2 yet to make a call. The problem seems to be twofold, poor UI, and poor implementation.

          You have to understand where I'm coming from. I'm no fan of Microsoft's practices or the stability or security of their code. And I am a big fan of OS X technology. A (mostly) user friendly operating system backended to a unix system, with all the unix tools and features I love. Plus I'm not railing on the hardware architecture or the OS core. Codewarrior on OS X beats the pants off Visual Studio on Windows in just about every category. But OS X's Finder, its front door as it were to someone like me, has some serious lacks.

          I'm pretty fast in Windows explorer, I have to be navigating between hundreds of source files. I've learned just about all the shortcut keys and my hands move to wherever is fastest to accomplish a given task, mouse or keyboard. When I started working on the mac I was frustrated by the amount of mouse effort I had to expend. If my hands are on the keyboard and I need to do some UI navigation I don't want to have to use the mouse. I call that poor UI. I know there are probably keys there I don't know about, but they certainly aren't readily apparent in the help files. The tab between controls functionality windows has seems to be largely missing. I'm not incapable of learning new shortcut commands, I just need to be able to find out what they are without installing 4 third party applications that add them.

          The seoncd part is that the finder is just damn slow. I don't care that its shiny and round and scales perfectly. I have a ~500Mhz G4 and thats more than enough power to make sure that simple tasks like moving files around and editing source code should never EVER have a perceptible delay. Sure, maybe Windows XP might be slow on an equivalently powered PC, but you know what? I can turn off all the UI crap that comes with XP. Not so with OS X. Its about as customizable as your grandmothers sofa, the one with the plastic covering you're not allowed to sit on.

  • I find Mac OS X slow (Score:4, Informative)

    by Adam Rightmann (609216) on Thursday November 07 2002, @04:42PM (#4619974)
    but that's because most of the apps I support are only supported in Mac OS 9, so I have to wait for the OS 9 emulation window to open up, slow, slow, slow.

    A good test would be with native OS X applications, compiled for OS X and not just emulating OS 9, but that's going to take a while.

    • by dildatron (611498) on Thursday November 07 2002, @04:48PM (#4620052)
      I find it a bit slow, but I consider my hardware marginal.

      I have a 500MHz G3 iBook, 384MB RAM, OS X 10.2. It is not really slow, but it is not as fast as my linux machine, a 750MHz Athlon, 640MB RAM, KDE3.

      I have not yet gotten the oppertunity to use OS X on a faster machine, but I suspect on a G4 processor it would be much better. Even on my G3, it is not so slow it makes me puke, it could just be a little snappier with IE, Mozilla, and opening up a terminal.
    • by MoxCamel (20484) on Thursday November 07 2002, @04:57PM (#4620187)
      Mozilla for OS X is the slowest OS X app I have. I still use it cause I'm totally addicted to tabbed browsing, but I sure wish it were faster.

      (I know this is not an OS problem, it's a bloaty Mozilla problem)
      • by sh4de (93527) on Thursday November 07 2002, @05:11PM (#4620384) Homepage
        AFAIK, OS X is late-binding by nature, but there's a way to speed it up by pre-binding. This process allows apps and libs to be loaded without resolving symbols in other binaries.

        In versions prior to 10.2, this was a manual process, usually run by the Installer app after installing a new package.

        10.2 updates prebindings for a new app automatically when it's launched for the time. There's a caveat: if you have multiple partitions, only apps on the boot partition will be pre-bound automatically.

        See the manual pages for update_prebinding(1) and redo_prebinding(1) for more info.
  • Not anymore (Score:4, Informative)

    by tral (223126) <tralfamadorian@excite.com> on Thursday November 07 2002, @04:42PM (#4619976)
    OS 10.0 was unbearably slow. They improved the performance with 10.1, and 10.2 doesn't seem to have any problems.
    • by Faggot (614416) <[moc.yag] [ta] [sdaohc]> on Thursday November 07 2002, @04:54PM (#4620139) Homepage
      When performing calculations, applying Photoshop filters, etc Macs are just as fast or faster than P4s of double the clock rate. Where Apple traded its speed is in the workings of its interface, and I think it was a good decision.

      Certain things do not need to happen instantly. In addition, doing them not-instantly allows plenty of eye-candy rendering and a soft user interface. Apple has tuned their OS to be fast to the program, and soft and comfortable towards the user.

      • by inkfox (580440) on Thursday November 07 2002, @06:01PM (#4620965) Homepage
        When performing calculations, applying Photoshop filters, etc Macs are just as fast or faster than P4s of double the clock rate.
        I'll start by saying that I'm a fan of the Mac. But there's little "etc" to your statement above. For select things which have been hand optimized to use the additional special instructions, there is a two-fold speed difference. But this isn't true of general case code, such as your typical spreadsheet calculation. No compiler generates anything like double-speed code without hand-tweaking, and this is very rarely done as it isn't cost-efficient. Doubling the speed of a recalc doesn't sell more copies of Excel.

        In addition to the above, the bus speed is most often the limiting factor with modern computers, and all but the rack servers are still limited to a 100MHz and 133MHz bus. The larger cache available on the higher end macs alleviates this somewhat, but doesn't solve the problem entirely.

        In addition to the above, consider that even if a two-fold per-clock increase were in place, you can get PC processors at more than double the lcock for prices competitive with Mac prices.

        What's more important is the Mac UI. It's laid out more conveniently, and there are standards which make mousing more efficient, and make the keyboard as effective as ever (contrast to the average Windows program, where the majority of the keyboard shortcuts aren't even listed, if they even exist).

        As you say, Apple has tuned the OS to be comfortable to the user. It has also made it more efficient for the user. Given that the majority of time time the computer is waiting for the user, and not the other way around, this is very significant.

  • by Gabey (18874) <gabesspam@yahoo.com> on Thursday November 07 2002, @04:44PM (#4620002) Homepage
    I recently installed OSX on my wife's iBook (366Mhz, 160MB RAM)...it previously had OS9.x on it, and it crawled. Neither of us would even want to use it, it was so bad.
    After installing OSX, it's runs amazingly well, and not just for the eyecandy, etc. Compared to other OS's, I would say it's right about on target...sure, it's a little sluggish opening Photoshop or having multiple browser windows open, but most 366Mhz machines are.

    I'm kind of surprised to see this question at all...OSX has struck me as very fast, all things considered.

    -Gabe
  • by Anonymous Coward on Thursday November 07 2002, @04:45PM (#4620007)
    For those Mac OS X users out there, have you noticed operations that seemed slower using Mac OS X compared to similar operations on other operating systems?

    No matter if they have, no true Mac user would ever say so, and you know it.
  • by 2nd Post! (213333) <gundbear.pacbell@net> on Thursday November 07 2002, @04:46PM (#4620029) Homepage
    For people who want to bash and criticise OS X, then of course it's TOO SLOW.

    For people who enjoy and love OS X, then it's not all that slow.

    There is definitely a class of people who need or want speed but don't have it, and they think OS X is slow. The hard part is figuring out whether their views and circumstances resemble yours so that you know whether to accept or discard their perception.

    My view: OS X on a 400MHz G4 is fine. Applications my have a performance constraint due to slow CPU speed, but actual navigation of the OS is not a problem.

    I also run OS X on a 933MHz G4. With a GeForce2, 768MB ram. Runs fine.

    Slow always depends on how you define fast. Web browsing rendering is a tad slower and less optimized than under Windows, but on the flip side the HTML engine isn't integrated into the OS either.

    And you really can't trust Microsoft to create a better browsing experience under OS X than under Windows XP, can you?

    I use Mozilla just fine, though.
  • os x, linux (Score:5, Insightful)

    by Aniquel (151133) on Thursday November 07 2002, @04:48PM (#4620044)
    I use both os x and linux pretty extensively. I've used linux on macs as well (yellowdog and linuxppc). Linux *is* faster, from a user experience point of view and from a systems standpoint - However, this is on older (400mhz) G4's. The new iMacs (and by extension the new PowerMacs) are *much* snappier, but they would be in linux too. Harkening back to a post from a few days earlier, os x has about 85-90% the raw speed of linux on identical hardware. Considering the UI and application base, that's good enough for me. Besides, if you wanted straight-up hardcore power, you wouldn't be using a ppc. You'd be using a .357.
  • VERY Slow (Score:5, Funny)

    by avandesande (143899) on Thursday November 07 2002, @04:48PM (#4620049) Journal
    I asked my mac to get me a beer from the fridge, and I am still waiting.....
  • ...read this article (Score:5, Informative)

    by jukal (523582) on Thursday November 07 2002, @04:48PM (#4620053) Journal
    Mac OS X 10.2 Makes Fast Break [eweek.com] at eWeek. I don't know anything about Macs but those rare people I kow using it, have said the same as the article:

    There were some speed improvements in Mac OS X 10.1, but this latest Mac OS version wrings significantly improved performance out of Aqua, courtesy of Quartz Extreme. This Apple technology offloads rendering of windows and other screen elements onto the graphics processing unit in a system's video card, which in turn lightens the load on the system's main processor.

  • LCD iMac (Score:5, Interesting)

    by Triv (181010) on Thursday November 07 2002, @04:48PM (#4620057) Journal
    I have an LCD iMac, and no, it's not slow - meaning: it does everything I need it to any I rarely notice the CPU usage go above 70% (unless I'm burning/Ripping a CD or, oddly, dialing in to my ISP). Personally, that's all that matters - I don't care how it compares to a PIII or whatever. It works great and that's that.

    However. I WILL say that OS9 is noticably faster (albeit WAY more unstable), particularly when gaming. Q3:A runs great under OSX but is a damn sight snappier booted into 9. Same thing with DiabloII, Starcraft or Baldur's Gate II.

    However (again). That could be because 3DFX support in OSX is a wee bit buggy - DII or BGII will run with 3d acceleration on but unplayably slowly. Don't have that problem in OS9. Go figure. :)

    Triv
  • well (Score:5, Interesting)

    by Auckerman (223266) on Thursday November 07 2002, @04:50PM (#4620081)
    "have you noticed operations that seemed slower using Mac OS X compared to similar operations on other operating systems?"
    Simple answer, yes. Complex answer: Those systems aren't running Windows. Mac OS X is always RESPONSIVE. If a splash screen comes up, you can still pull another application in front of it. If an app is running a huge calculation, you can still web browse. iTunes doesn't skip. You can play DVD on your background (you have to set your background color to a specific value, start up the DVD, then hide the DVD player). You put a really pretty fish tank OpenGL screensaver as your background. Running many mpeg4s at the same time doesn't choke the system. It keeps going, in fact if you just add ram, like with any Unix system, you can throw any number of big jobs at it, and it will keep going.

    That being said, you have to wait for the genie effect to take place. Because it's a friggen animation. Same with icon removals from the desktop. If you aren't running QE (which from what I know is most of the OS X installs today), you get a big CPU hit on moving windows, resizing, and putting in dock. But it still keeps going. I'm really quite amazed at how well it works, day in, day out.

    Am I unpleased, no. Do I even consider other OS's. Not anymore. Can it be made faster, sure.
  • Speed (Score:5, Interesting)

    by WatertonMan (550706) on Thursday November 07 2002, @04:54PM (#4620136)
    OSX is a memory hog - even worse that XP. So if you are running it with less that 3/4 of a Gig of memory, invest in the memory. I think you'll change your opinion on speed then.

    It still isn't as fast as Linux or XP (IMO), but has enough polish that I still prefer using it. There are some things that count more than speed. I think OSX does well on those.

    I must ask though why these rather generic OSX discussions keep coming up on Slashdot. They seem more appropriate for some forum rather than "news for geeks." Don't get me wrong, I love OSX. I can't wait for 10.3 which will probably be the final reason to pick it over other OSes. But does it really justify all these topics?

    • Re:Speed (Score:5, Interesting)

      by drinkypoo (153816) <martin.espinoza@gmail.com> on Thursday November 07 2002, @06:13PM (#4621078) Homepage Journal
      But does it really justify all these topics?

      The real question: Does it really justify the aqua-fresh toothpaste (wonder if that's where the name actually came from) look of slashdot's mac section?

      OSX justifies all the topics because it appears to be exactly what we (the people of the geek republic of Terra) have been asking for all along; A major-vendor (Apple is close enough) operating system which supports current desktop apps through a new API, legacy desktop apps through a virtual machine, which looks really great, and has Unix at its core. Unfortunately, it comes from Apple, which means it only runs on expensive custom hardware, which makes it useless to most of us, who will have to wait for Linux to reach a more mature level. It's interesting that OSX is more useful as a desktop Unix than Linux is (for the non-technically-inclined user, someone who may be technically competent but not used to ripping things apart and making them work when they're broken) even though it's fairly new, whereas Linux has many years on it and still has a lot of stability, speed, compatibility, and usability problems as far as the desktop goes.

      On the other hand, MacOSX had NeXTStep to work with. While there was an x86 clone version of NeXTStep, as I understand it was fairly tightly bound to a small selection of hardware, making it a more similar product to MacOSX than it might at first appear, and of course it was best-known for running on the various NeXT slabs and cubes, which might as well have been next-generation macs.

      So yes, since it aims to fulfill all our dreams of what an OS should be (fast (maybe), easy (yes), powerful (certainly), stable (maybe)) it does justify this number of stories, and more. We have traditionally been informed every time a new linux kernel comes out, and MacOSX will directly touch more lives than linux will any time soon.

  • by macthulhu (603399) on Thursday November 07 2002, @04:54PM (#4620137)
    As I'm sure many of the people about to post here do, I use several different OSs during the course of my day. Once I leave work, I rely on OSX for me personal machine. Even with 10.1.5, almost everything seems faster than any flavor of Windows that I come into contact with. My home machine is a "lowly" Dual 533 G4 with a Gig of RAM, and it consistently performs better than any of my other machines... ranging from a dual 600 Pentium w/ NT4 to 2GHZ AMD w/ XP. I am running mostly Multimedia creation software, so maybe that's where the results come from... Anyway, OSX is plenty fast... except for some strange spinning beachball zone-outs at weird times. To be honest, even though I am one of those Mac people that will break a bottle on the bar and hold it to your throat for bad-mouthing my system... I am perfectly functional with Windows going all the way back to 3.11. Bottom line: OSX on a sufficiently pumped up G4 will get the job done, and get it done pretty quickly. Now back to the impending flame war...
  • 10.0.0 Public Beta was barely usable, in every way. It was beyond slow. It was almost a toy. The genie effect took forever.

    10.0.0 release was slow. It was a pain.

    10.1.0 was improved; my machines are quite old, and it showed.

    10.1.5 was improved; as the last of the 10.1 branch, it showed improvement.

    10.2 brought a noticeable improvement. I wasn't spurting my shorts but I could not recommend it to others without hesitation, with the exception of the guys that buy a new CPU every time AMD or Intel comes out with one, because the old was one "just too slow". Whatever.

    Is everyone seeing the trend? Getting better all the time. I forgot who did the presentation, but the quote was along the line of, "We have to improve in software because we can't trust Motorola to speed up the hardware". Each new release boosts performance on the same hardware with no noticeable new bugs or problems (other than what Apple introduces on purpose, like breaking LiteSwitch w/ 10.2).

    In short: it's sad that the unacceptable performance of older versions, esp. betas, has tainted a great OS with the moniker "slow".
  • by PineHall (206441) on Thursday November 07 2002, @04:56PM (#4620178)
    http://www.byte.com/documents/s=7692/byt1035828368 066/1028_bar.html [byte.com]

    Moshe Bar says: "The fact that OS X needs to improve in VM and I/O handling is understandable given its relatively young age." That is his opinion from testing XServe. (Note there was things he could have done to improve the test, but on a whole it was a good test.)

  • Not really. (Score:5, Insightful)

    by Jobe_br (27348) <bdruth@gma i l . com> on Thursday November 07 2002, @04:57PM (#4620202)
    It all depends on what you're doing and how much you're doing of it. At work, I have a Dell Optiplex GX150 with a 1GHz PIII processor, if I'm not mistaken. This system has 256MB of RAM and runs Win2K SP3.

    Typically, if I have 4 apps open (Outlook, SciTE*, Phoenix or Moz, PuTTY*) - when I launch IE, its unbearably slow - the screen redraws visibly and the system is generally unresponsive for the ~5 seconds it takes IE to launch. Not sure what causes this - 256MB of RAM is obviously part of the problem, but the swap file shouldn't be that slow, either.

    Recently (this past Tues.) I was at home working on a few different things - ripping CDs to AIFF w/ Audion 3.0.2 (in batch mode), backing up 10GB of data from a ~19GB partition on a FW drive to a 8x4x32 CD-RW in an external FW enclosure (Dantz Retrospect Express), editing PHP files in BBEdit (6.5.2), updating site files in Dreamweaver MX whenever my partner needed something updated, checking mail via Chimera/Mozilla using Horde/IMP (web mail access), maintaining a connection to an FTP site (authenticated) and SSH site (publickey) for files I was editing in BBEdit and for Apache log files I was copying down to run through the Summary.net analyzer which was also running and serving out log stats to two clients who wanted temporary stats on certain logs (not available on our main server). Summary was also doing DNS lookups and crunching log file entries in the background while everything else was going on.

    Now - was my computer slow? Well, Chimera/Moz seems to have a bug in entering data into text areas when the system is under high-load - that was unbearable. Otherwise, besides having to wait a couple seconds to switch desktops (using Space.app), other apps responded just fine. The multi-tasking on OS X is first rate, it really is. I managed to rip through ~15 CDs that day, in about an 8 hr time frame, while I had an amazingly productive day otherwise.

    I'm running a classic iMac DV at 400MHz with a G3 system, unaccelerated by Quartz Extreme, as my AGP card only has 8MB of video RAM. If I can be productive on a system like this (and I have a pretty low ctrl-alt-del threshold, as a former prof used to call it) - then you ought to be just fine with one of the 15" iMacs running at ~700MHz with a G4 processor (which has Altivec - amazing, don't ignore that) and a few other enhancements over my machine.

    Slow is all in the eye of the beholder. I know people that always use the fastest of the fastest machines from Intel when they come out. People like that will never be satisfied. I've had this iMac for almost 3 yrs now and every release of OS X has run faster (noticeably). Menus pop out faster, Finder responds faster, file searches execute faster, applications launch faster - the works. I look forward to my next hardware upgrade, just like the next guy, but for being productive - I can kick ass on my machine, and I give a lot of credit to OS X. My productivity is limited in various fashions on my Win2K machine at work - crashes cause some delays, but more minor annoyances cause far more delays.

    Cheers.
  • by Wonderkid (541329) on Thursday November 07 2002, @04:58PM (#4620218) Homepage
    As a designer, I have been using Macs full time since 1991. Currently, I am running OSX 10.1.5 on a 500Mhz G4 Powerbook with 384Meg RAM and 20gig hard drive. Am using Photoshop 7, Illustrator 10 and other latest versions of OSX native apps and they are much slower in launching and feel sluggish over their OS9 counterparts. OS9 was 'snappy' and the less complex window borders and smaller typefaces provided more screen / desktop real estate. Not only that, but the file / directory dialogs are a pain and the lack of smart window re-sizing/tiling like MS Windows means constant manual window re-sizing. OSX breaks several GUI guidelines that OS9 adhered to. The hype concerning OSX is only justified because of Apple's wise decision to base it on Unix, meaning it is stable and geek friendly. Apps do quit once in a while, but unless OS9 under classic mode goes weird, you never need re-start. Anyway, I think people are praising the wrong creation from Apple. What justifies buying a Mac over all else are apps such as iPhoto, iTunes, iMovie etc that are a pleasure to use and totally invaluable on a daily basis. But it's not OSX that makes them great (iTunes was identical under OS9 from an operational angle), it's the people friendly design and functionality.

    Remember, these comments on OSX all based on 10.1.5, not 10.2 (Jaguar.)

  • by Malic (15038) on Thursday November 07 2002, @04:59PM (#4620221)
    Simple file moving operations can take FOREVER if you are moving around hundreds of files. Though I haven't tried it, I am sure that from the command line, it could be a blink of the eye.

    Example: Select, say 600 MAME ROM .zip files, and move them to another folder that already contains 3000 MAME ROM .zip files. Some may exist already and need to be overwritten and some files are new ones.

    An operation like this on Windows takes very little time to do. MacOS X can take many minutes to do the same. I don't understand why. This is on a G3 500Mhz iMac DV w/1GB RAM.

    The underlying OS is very fast. The GUI/Finder needs all the help it can get. Even after 10.1 and 10.2!
  • My observations (Score:5, Interesting)

    by thatguywhoiam (524290) on Thursday November 07 2002, @04:59PM (#4620225)
    Disclaimer: I have a G4/466 (OS X) at home, and I regularly use a 1.6Ghz Athlon at work (Win2000).

    I think the question is really one of perceived speed. I noticed that on the AMD box, and Win2000, the common behaviour for screen draws is to wait until the operation is finished, then draw all-at-once. For example, IE, when loading a page, will remain exactly as it is (the current page you're on), until such time that it loads Slashdot, then draws it in one fast swoop.

    Now, OS X does this as well, but it tends to give more feedback. The browser window will turn white, then the banner appears, then graphics and text. I've timed both boxes - they render within a half-second of each other (again, subjectively). The OS X box could easily give the impression of slowness. But it isn't really.

    There are some things in OS X that need improvement - notably window-sizing - but then again, the Win2000 box still does outline-drawing for resizing so it's not fair.

    In the end I think Quartz Extreme is Apple's answer to this. Quartz does a hell of a lot more work than the current Windows drawing scheme, and it looks a hell of a lot better. When OS X first appeared, many lamented the excessive eye-candy. Now we have a scheme where your normally-dormant hotshot GPU is helping out with drawing the OS. It makes a gigantic difference, and takes a major load off the CPU. But it is version 1. It will get better.

    I expect Microsoft to go through similar growing pains when they go for the photorealistic desktop in Longhorn.

      • by tim1724 (28482) on Thursday November 07 2002, @06:42PM (#4621341) Homepage Journal
        Haven't Linux and Windows used acclerated hardware video drivers for drawing their GUI for many years? I'm talking about Windows 95 era, possibly even WFWG 3.11. I'm sorry if it only takes a $30 "hotshot" graphics card to accelerate the rendering of a perfectly usable 2-D GUI in X or Win32, but them's the breaks.

        yes, they use 2D hardware acceleration for drawing. So did Mac OS 9 (and 8, and 7) .. Quartz Extreme is something completely different. It doesn't accelerate drawing, it accelerates compositing

        Quartz has two parts:

        • Quartz 2D: This does the drawing of 2D primitives (lines, rectangles, bezier curves, etc.) in windows... it might be accelerated, it might not be. I'm not sure. Given that Aqua uses mostly Bezier curves and bitmaps, plus the fact that it supports transparency and floating point coordinates, I don't think most 2D hardware would do much to accelerate drawing. (standard 2D hardware doesn't usually do bezier curves, floating point coordinates, or transparency)
        • Quartz Compositor: This is the part of Quartz which composits all your windows together for display on the screen. Remember that windows are transparent in Quartz, so a particular pixel on the screen may need to be calculated from the cumulative effects of drawing multiple semi-transparent windows, drop shadows, etc. This is slow in software, but this is exactly the sort of thing that 3D hardware does really well. So on a graphics card supported by Quartz Extreme (recent ATI or nVidia cards with 2x or better AGP) this is all done in hardware. Quartz 2D draws into windows the same as it always did, but instead of having Quartz Compositor composite the windows in software, Quartz Extreme just passes the window contents as textures and passes the window coordinates as the vertices of rectangles, and lets the hardware render your desktop as a bunch of texture-mapped polygons :)
  • by x mani x (21412) <mghaseNO@SPAMcs.mcgill.ca> on Thursday November 07 2002, @05:11PM (#4620373) Homepage
    I had a G4/533 with a gig of RAM. General performance is just fine, non graphical applications like Apache, gzip, etc would have performance up to par with the same software on any other OS and/or platform.

    The main problem was the graphics rendering. I haven't tried Quartz Extreme, but on 10.1, things like scrolling in Mozilla (this includes Chimera) or IE were just sluggish. Scrolling a web page, in the Intel world, should only be sluggish if you're using a Pentium 100 with an non-accelerated graphics card.

    Resizing a window in OSX has the same issues as scrolling. The last time a Windows or Linux user experienced sluggishness and frame skipping when resizing a simple file manager or browser window was like ... 1995.

    I think what OSX needs is a means to bypassing the graphics pipeline for certain operations. One way I did this was by loading up IE for OS9 in OSX ... it doesn't anti-alias/scale/whatever, and it scrolls and resizes fast. Although this feature might not be needed if QE absolutely solves the above problems. But wait, my G4's Rage 128 pro wouldn't work with QE.

    The kind of UI sluggishness I describe is a really hard pill to swallow for a traditional PC user like me. I switched, but after a year ended up switching back. It's just like the time I bought an SGI, once I got over the fact that "wow, I own an SGI workstation!", it quickly became a cool purple doorstop. Once you get over having "real" transparent terminals, all you're left with is a slow user interface. Maybe OSX is a couple years ahead of its time?

  • by goombah99 (560566) on Thursday November 07 2002, @05:13PM (#4620407)
    I recently spent some time evaluating mac,athalon,pentium,athalon benchmaks using scientific fortran that i had written for protein structure analysis. We were buying a large 500 processor cluster so I wanted to get it right.

    Since I was buying a cluster my criteria was not single processor speed but speed per dollar what i found was mildy surprising. For programs that could take advatage of the altivec chip inside the G4, the mac was about a factor of 2 cheaper per run time than the P4 and athalons. On the otherhand with the Altivec turned off the mac was about a factor of 2 more expensive per run time. I note that this was not done on code optimised for the altivec but was just generic fortran passed through an automatic vector pre-processor program for compile time optimization.

    Of all the processors I tested, P3, p4, athalon, the P4 had the wildest variations in benchmarking. that is all the other proceesors seemed to have constant scaling factors in speed as the applications varied. but the p4 variev by over a factor of 3 from the others both faster and slower. I assume this has something to do with the very long pipeline, and the hyper threading, and the size of the caches. But even taking these into account I found it highly unpredictable which applications would run faster or slower (that is ones that might logically have more cache misses did not neccessary degrade)

    . In the end I decided the P3 has the most bang for the buck , though falling cpu prices might shift that conclusion to the athalon. The problem I encountered with the athalon was a higher down time for the cluster units due to thermal faliure., so thats a hidden cost. The apples NEVER failed in any thermal tests so thats a hidden plus.

    Now this analysis does not factor in other things like Graphics speed other factors more important to users than sceintific apps. However when I compare my molecular visualization grpahics before and after the release of 10.2 I have to say the mac is insanely fast for graphics now wheere before it was intolerably slow.

  • by Van Halen (31671) on Thursday November 07 2002, @05:20PM (#4620508) Homepage Journal
    Something I've noticed is that there are very widely varying accounts of OS X's speed on various hardware. To some people it's unbearable, while to others it's snappy. Let's try to take a look at some of the factors:
    • Opinion. Yes, most Mac lovers will tend to rate OS X as faster than Mac bashers will. Part of it is blind allegiance to or against the cause. The other part, I think, is that UI responsiveness doesn't seem to matter to many folks beyond a certain point. So what if your window resizes in 0.2 seconds rather than 0.00005? Yeah, if you sit there resizing windows nonstop, it'll hurt, but for most people that's not a big deal. What makes OS X great for many of us is that it allows us to work faster overall, regardless of whether certain things take a second or fraction thereof longer than on other platforms.

      Along these lines, some people can put up with a much more sluggish UI - thus the "I run OS X on my Mac Classic and it runs fine!" posts. And on the other end of the spectrum, anything less than instantaneous is unacceptable to some people. Again, I think allegiance one way or another can play a part in this.

    • Jaguar? When someone says OS X is slow, make sure they're talking about Jaguar. If not, it's pretty meaningless because Jaguar did come with major improvements in speed. I was skeptical, but I noticed the difference immediately after I installed. Not an "I think it may be faster" placebo effect, but measurable results. My time from login to when I could actually do something went from 30-45 seconds down to 2. Why was it so slow in 10.1? No idea, but thankfully Jaguar fixed that. Applications open in one or two bounces instead of 6 or 10. Plenty of room for improvement, but fast enough that I don't find myself waiting for the machine much these days.

    • Installation. Before installing Jaguar, I'd read that installing some of the extra localization packages and Japanese fonts can slow things down considerably. I made sure those were unchecked, so I can't comment personally on the difference, but I have no complaints with my setup!

    • Hardware. Obvious. The biggest factor being memory, the next biggest being machine model/CPU. If someone complains about OS X being slow when they're running out of memory, well, duh.

    That said, my own personal opinion is that it's fast enough for me. I run it on a G4 733 MHz tower and a 600 MHz iBook. In general, speed is such a non-issue that I never think about it. I have plenty of things on my wishlist for OS X to improve, and while speed is there, it's not terribly high. I don't find myself ever frustrated by a lack of speed with anything. I use iMovie, iDVD, XDarwin, Mozilla/Chimera, Quicken, iTunes, Terminal, and plenty more pretty extensively. Again, take my hardware, OS version (Jaguar) and personal biases (like Mac, OS X) into account.

    Even so, lately the iBook has been taking several seconds to login, where it used to be about 2 seconds when we first got it. Not sure why, but cleaning out ~/Library always seems to help. If not that, then it's probably something in /System or /Library. I'm not too thrilled that OS X seems to exhibit its own version of "registry rot," slowing down over time. I'd like to say that sort of problem only afflicts MS users but it's not my experience with OS X. Hopefully they're working hard on fixing and optimizing this stuff - and before it gets to a point where I do think it's too slow!

  • by mgerber (19521) on Thursday November 07 2002, @05:52PM (#4620866)
    I've got somewhat extensive experience using Windows XP, MacOS X, and Linux. These are my impressions based on a combination of subjective user experience and objective benchmark information I've found through research. I recommend that anyone seriously pondering this issue do their own research, particularly to back up the benchmark comments.

    First, let's get my biases out in the open: I am a Macintosh user by (recent, OSX only) preference who's also perfectly comfortable assembling Linux or Windows PCs from bare motherboard and case right on up. I prefer UNIX-based operating systems for their stability and openness, the more stable and open the better, but find Windows inevitably the best practical choice for some situations.

    I won't comment on disk and memory performance; others here have handled that ably, and I have no experience with MacOS X in very high load situations.

    Processor Performance

    This is the one that's subject to the most advocacy; raise your hands if you haven't heard the term "Megahertz Myth". Any hands up? Didn't think so. (Apple advocates aren't the only folks who like it; you'll hear it from AMD lovers, too.)

    G3 and G4 processors run at far slower clock rates than P6-class processors. This much is objective. What Mac advocates like to claim is that G3 and G4 processors are much faster, clock for clock, than P6-class processors. The problem in evaluating this claim is that it's both false and true at the same time.

    The G3 and G4 are not faster than P6-class processors at typical integer and floating point operations. They're just not. In fact, they tend to run (slightly) slower, clock for clock, in SPECmarks. They're only faster in one specialized world. The catch is, that specialized world is a major one.

    Vector and matrix operations are useful in a ton of multimedia applications--most particularly image and video editing, but there are other applications as well. The G3 and G4 have much better vector units than P6-class processors. Not better, much better. This is why Apple always uses Photoshop as their benchmark: a G4 running well-optimized vector math is entirely capable of spanking a P6-class processor running at twice its clock speed or more.

    So the answer to this question is that there is no definitive answer. Mac advocates will claim that graphical operations are the slowest things anyway, and so optimizing them will give you the most performance benefit overall. PC advocates will make the generalist argument, and include the (true) fact that an application must be hand-optimized for the G4's vector unit to see these performance gains.

    Overall, most people think the G3 and G4 are slower for most purposes, and that the Mac won't have a serious chance at the top of the performance heap again until its next round of processor upgrades, coming next year.

    UI Performance

    This is the performance most people notice. I'll hit several areas of it, since there are tradeoffs.

    First, the good. Aqua's overall responsiveness is probably the best of the three major windowing environments. Any of them can feel like they lose clicks or take forever to process them at times, but it generally feels like it happens less with Aqua than with either Windows or X. (Note that in X it's heavily dependent on what your desktop environment is--but most people like to use either KDE or GNOME, both of which have responsiveness issues.) Aqua also redraws on application switching faster than Windows does, and at about the same speed X does, since it handles open frames in much the same way.

    Now, the bad, and it's significant. Aqua is the heaviest of the three major windowing systems; it has more and more complicated screen elements than either X or Windows. It is about as fast as Windows at drawing individual screen elements (both are faster than X under most driver configurations), but overall, it feels the slowest of any of them at general UI drawing tasks. There are also some operations--like scrolling or resizing complex frames--that are just embarassingly slow.

    Overall, I like Aqua for its stability and prettiness (fonts look better on Aqua than any other UI, period), but I can see why its overhead irritates many people, especially those who've heavily customized and optimized an X setup.

    That's my $0.02. Hope it helps.
  • by sakusha (441986) on Thursday November 07 2002, @05:54PM (#4620883)
    I get tired of people stacking the deck against Macs by claiming Macs cost too much, then inventing some insane price out of thin air, like $4500. You'd have to build a pretty high end config, like a dualie 1.25Ghz with an Ultra160 RAID. Sure, you can build a wintel dualie hotbox and get up in the same price range. But I'm blazing along on a midrange dual 1Ghz machine, and oh man is it fast, and only $2500. So what is the point of attacking a Mac on price and claiming you can't get a machine except by paying $4500?!? Even an XServe doesn't cost that much.
    Anyway, I've had amazingly good performance in MacOS X, but there were a few rough edges at first. Finder was kinda slow on my old G3/400 and G3/500 machines, like sorting by kind in list view. They're getting some of the metadata stuff sorted out, the new Jag finder is all fixed up and speedy. The only laggy app seems to be the Terminal, which could use a replacement. But the core Unix apps have excellent speed. I put my old G3 into use with Apache & Quicktime Streaming Server, I'm amazed at how well it performs.
    Anyway, someone commented that MacOS X is hard on the apps but cushy on the user, or something like that. Right on. That was one of the Mac's big innovations, the GUI focused on the user. When I am running something like Final Cut Pro, I want every GUI screen gadget running full max. I want every single iota of computing power focused on ME and helping me get through the complex task. This is both the Mac's greatest feature and biggest CPU bottleneck. It's like the olden days of OS 9 before preemptive multitasking, when you held down the mouse, the whole CPU would hang until you let go of the menu. Whenever you were issuing commands, the CPU gave up control to the user. It was a CPU bottleneck, and we LIKED it, it gave the MacOS the immediacy of operation, a feeling of being in control that other OSes lacked. And I think they've translated that well into MacOS X. The system GUI still remains responsive, even when you're running CPU-intensive apps. Apps like Cleaner mpeg2 compression are as CPU-intense as it gets, it can compress 1 minute of DV video in 50 seconds on my midrange CPU. Cleaner is dual processor and Altivec aware, it maxes out both my CPUs, it's as hard a CPU workout as I have found. And it still leaves the system responsive, not locked up and CPU-bound.
  • by overbom (461949) <mike@@@smartphoneexperts...com> on Thursday November 07 2002, @05:58PM (#4620925) Homepage
    It's plenty fast, but not as fast as I wanted. So I sped it up. Here's what I did for my machine; some of it is what I routinely do to other people's machines. ymmv. ymmm. yumm.

    First, I advise all 10.1.x users to upgrade. Then again, I work for a school, and teachers can get 10.2 for free. It's worth it. I don't care that it should be free. If you want better performance, stop griping, or run OS9. OS10.0 and 10.1 are not optimal for ordinary use.

    make sure you're following the recommendation for Video RAM -- 16MB, Quartz Extreme pretty much needs it. If you can't upgrade a card, cram as much memory as you can in there, you will need it.

    I wouldn't attempt to use a OSX machine with less than 256. All power users get 512MB by default.

    There's an option on the installation disk (under the disk utility option, maybe?) that will reset permissions on the OS. I've noticed this would speed up a slower computer; it takes about 1/2 hour on my laptop.

    Turn the machine off once in a while. I suspect OSX's memory garbage collection isn't as good as it could be. I reboot the laptop about once a month, (after I've had a finder crash, usually).

    if you've got a laptop that isn't on at 3 in the morning, run the periodic files (i.e., let cron do its thing). Someone released an app that does this for the shell-feary; I forget its name. Google loves you.

    Use a valid hostname. Something called "Foo's Computer" isn't valid DNS, even though it's the default (bad apple!). This will affect how long it takes to connect to the network, esp. at boot time. Having DNS entries (and reverse DNS) helps a bunch, if you're using DHCP (there are opts in bind to autofill this for you). Valid hostnames include a-z, 0-9, and "-". Have fun and be creative.

    Disable what you don't need. I edited the scripts in /System/Library/StartupItems. Say Goodbye crashreporter, appletalk, and rendezvous. I was nice and had my modifications listen to /etc/hostconfig, in case I wanted to re-enable them quickly, at a later date. Most other people need networking, I've noticed, but I just need scp and ftp. ;P

    prebinding question. Run as root (use sudo, or, um, use root)

    update_prebinding -root / -force

    And wait for a bit, watching a bunch of errors spring up because the printer apps weren't prebound. You might want to do an output redirection (add something like 2&>1 ~/prebind.log to the command [or is it 2>&1?]) if you want a record of what it did.

    here to help,

    mike
  • by bperkins (12056) on Thursday November 07 2002, @08:56PM (#4622176) Homepage Journal
    Other topics that are perfect for objective debate such as:

    Is Emacs slow?

    Is vi easy to use?

    Is perl a good language?

    Do you like RMS?

    Is your mother ugly?

    Is Christianity the best religion?

    Cowboy Neal?
  • Perception (Score:5, Interesting)

    by harlows_monkeys (106428) on Thursday November 07 2002, @11:49PM (#4623118) Homepage
    I think a big part of it is that quite a few OS X apps do things in a way that makes them seem slower than they are.

    Take IE, for example. It seems to wait to display the page until it has the whole thing ready to render. On a big slashdot story, that can take a while. Compare to, say, most browsers on Linux, which seem to display while the page is still downloading. Browsing seems way faster on my home system on a 144 Kbit/second connection with Linux than it does at work on OS X on a T3.

    On the other hand, I do have evidence that the Mac is actually slow. E.g., when I start to load a slashdot page at work, I often give up, switch over to the XP machine on the KVM switch, and go load it there, and finish ahead of the Mac. The XP machine is an ancient P2 400 with 384 megs of RAM, the Mac is an ancient B&W G3 300 MHz with about 600 meg of RAM, so the machines are comparable (both pathetic by modern standards, but comparable). So, it actually appears that the Mac is slow at browsing, and IE works in such a way to emphasize that slowness, making it seem unbearably slow.

    Also, a lot of apps, and Finder, aren't as threaded as they could be. While IE, for instance, is busy getting that big slashdot page ready to display, the dreaded spinning color-ball shows up, so you can't switch back and view the other pages you were reading.

    Finally, much Apple software IS slow. There's a thread on comp.sys.mac.advocacy about this right now, where someone was saying that the new generation of iApps seem slower than the previous iApps, and pointing out an apparent correlation between those written in Carbon (fast) and Cocoa (slow). However, other people have pointed out examples of fast Cocoa apps, so that is not the problem. Most interesting was someone who wrote their own photo manager, and compared to iPhoto. For some things, his is 2 orders of magnitude faster than iPhoto. Evidently, Apple simply used crappy algorithms in iPhoto. Apple's mail program is similarly problematic when mailboxes get large. A lot of people on comp.sys.mac.advocacy have given up on it and switched to Eudora, and report their Macs are nice and fast at mail then.

    • Re:HAhah (Score:4, Insightful)

      by johnpaul191 (240105) on Thursday November 07 2002, @04:49PM (#4620072) Homepage
      still waiting for the windows users to post? heh

      i am running an older mac... G4 400mghz running 10.2 with a gig of ram..... i think the pokeyness IS application specific for the most part. i upgraded my Rage128 card to a 7500 when i hopped to 10.2 and noticed it handles the aqua interface a lot better. there are also little things to do to zip up the OS (like under dock prefs switch from "genie" to "scale"), turn off dock magnification, don't use a 10 megapixel picture as your desktop.

      obviously it's not as efficient as a very tweaked Linux or BSD box (with fast innards), but as an out of the box OS it's very usable. as always it's better running on newer machines, but i can use it on an older crt iMac G3 300mghz and not bang my head against the table. you might not want to do intense av work on that machine, but for day to day tasks (which iMacs were intended for) it will do just fine.