Slashdot Mirror
Mac OS X Slow for Web Browsing?
Atryn writes "Wired News has reportedly confirmed user performance complaints in their own tests. From the article: 'That was a conscious decision Apple made,' Mac MSIE project manager Jimmy Grewal said. 'They optimized for user experience rather than raw performance.'" My hunch is that you can take care of many Mac OS X performance issues by logging in as user ">console" ...
Chimera is, according to these tests, the fastest MacOS Web browser by a factor of 2.
Chimera is, of course, based on Gecko, the Mozilla rendering engine. It's mainly the work of Mozilla uber-hacker Dave Hyatt.
Gerv
You'd have a hard case arguing that OSX doesn't have room for improvement speedwise, but it's this horrible thing that some people like to pretend that it is. Some of the blame goes to Apple, some goes to the application writers. Mac IE renders some stuff painfully slow. I don't know why. Like the article said, things like slashdot comments feel like they're taking all day. In reality, it's only 5 seconds, but we all know what sort of attention spans people have nowadays. There's a pretty new browser called Chimera that is early in development, and still has a limited feature set, but it renders things almost instantly, including slashdot comments. So there isn't some inherent problem within the OS that makes it impossible for your applications to function reasonably.
Not to sound too much like an apple apologist, but they've done quite a bit to get OSX to where it is so far, and the more I use it, the more I appreciate where it's advanced over OS9. I don't mind waiting a bit for things to improve. Just like I don't really mind anymore waiting 5 seconds for IE to throw together the comment threads. Most of us could benefit from learning a little patience.
Although I would surmize that it's apple's fault that they get judged so harshly. Seeing as steve jobs claims that every time someone in their company makes a sketch on a post-it note, they've created a new revolution in the world, people are justified in being extremely critical.
One time I threw a brick at a duck.
The problem is in the Tasmin rendering engine used by IE for Mac. But blaming Apple seemed to be the easiest thing for them to do.
There are certainly performance problems in OS X's UI, but let's give blame where blame is due.
-jon
Remember Amalek.
The main issue is the Internet Explorer still runs off of the "Classic Event Model" where it constantly polls for new events. The newer Carbon event model supports those old methods, because EVERYONE used them in the old system. Think how much CPU that takes when all those old programs (even though they are "carbon compliant") are constantly jumping up and down asking if they've gotten an event.
o n/ CarbonPortingTools/carbonportingtools.html
The new "Carbon Event Model" allows you to associate events with handlers, and when an event fires that you'd like to pay attention to, your call-back gets fired. Much more effecient.
The cocoa event model is even more robust.
The problem lies in that programers were able to compile a "carbon compliant" application, without moving to these new event models. THIS IS GOOD. Imagine how PISSED off a developer was if they were told, "Yea, you have to move all your event code over to this new system, cause it's better." No. A developer would rather have a product up and running on OS X natively, and then move over.
Anyway, it's not that Apple has "buggered" up the system someway, the applications have exploited the API's that Apple has made available, but it was a necissary evil.
http://developer.apple.com/techpubs/macosx/Carb
Has information about the carbon event model, and high performance computing.
- Sighuh?
Recently, I'd been having some performance issues with Mac OS X on my titanium Powerbook 500. (256 meg of ram on 10.1.4)
/var/run/cron.pid, but don't quote me...)
The problem was that EVERYTHING gave me spinning beach ball. File operations, minimizing Finder windows, you name it...Even scrolling in MOzilla and IE were affected. Then I read on MacAddict that OS X needs to be left running all night so that various "cleanup" tasks can run.
Anybody who has OS X should consider leaving there machine up all night so these run... It will resolve a great many problems that you're having, and allow us to go back to bashing MS and Oracle instead of Apple...
Unix people familiar with cron should have no problem with editing the cleanups to run at a more reasonable hour than 3am, 4am, and 5am (like one when your machine will be running)... (I think the file to edit is
Alternately, if you're a regular mac user and don't feel like mucking about with the terminal, hit Version Tracker and pick up MacJanitor. It's a friendly GUI that lets to schedule your daily, weekly, and monthly jobs, or trip them manually on demand.
Since I'd used the machine, it had never been awake all night (I close the lid when I go to bed, usually before 3am...) so cron had never done anything to optimize my machine.
Now? All better. Faster than I remember 10.1.1 being...
Who did what now?