Slashdot Mirror

← Back to Stories (view on slashdot.org)

10 Things Apple Did To Make Mac OS X Faster

Posted by ryuzaki0 on from the road-to-betterment dept.

bariswheel writes "This kernelthread article seeks to investigate further to the inner core of OS X and the improvements therein. The subtopics are the following: BootCache, Kernel Extensions Cache, Hot File Clustering, Working Set Detection, On-the-fly Defragmentation, Prebinding, Helping Developers Create Code Faster, Helping Developers Create Faster Code, Journaling in HFS Plus, and Instant-on."

2 of 375 comments (clear)

  1. Re:Dupe several years later? by ArsonSmith · · Score: 0, Troll

    Ohh great idea!!! lets encourge dupes. Why do we even need new articles just start over from day one of slashdot and start posting all the old stories.

    Wonderful...

    --
    Paying taxes to buy civilization is like paying a hooker to buy love.
  2. Stupid, stupid, stupid. by Lost+Found · · Score: 0, Troll

    This is retarded. Mac OS X - which is based on one of the slowest operating systems in the history of UNIX (Mach) - performs terribly. Microkernels were a terrible idea in practice; that's why everyone moved their shit into kernel space (and gave up the benefit of having a microkernel in the first place).

    It took Apple until the Tiger release to make the kernel's locking scheme any finer than ONE network lock, and ONE "everything else" lock. Reminds me of the days of cli()/sti()/lock_kernel() in Linux. (In Tiger, there are something like 5 or 6 locks -- still a disaster.)

    The funny thing is when Anandtech did a Tiger review some time back to measure the performance. Considering the delta between modern Linux and OS X (Linux measuring in at ten times faster in some places), it's outstandingly shocking that anyone would say OS X performs at all. Windows puts up a *much* better fight.

    http://www.anandtech.com/mac/showdoc.aspx?i=2436&p =1