Impressive Mac OS X 10.6 “Snow Leopard” build 10A335 seeded

Despite being a mere 21 builds apart from the previous seed, 10A314, released earlier this month….the latest Snow Leopard seed (simultaneously released in both Standard and Server versions) has definitely taken a big step forward in many areas.

Several elements of the full internal Mac OS X 10.6 code tree, such as the “Marble” interface revamp and overhauled Finder as well as the entire PowerPC version of the operating system, continue to be withheld from the developer builds — but even absent those more visible features, Snow Leopard is truly beginning to shine and show full potential with the advent of 10A335.

Performance is a notable area of big improvement since build 314 was released at the beginning of April; already stunningly fast, sources confirm that 335 removes a significant amount of debug code which always bogs down developmental versions of OS X as compared to their final-release counterparts. Several developers have reported to Rumors that on even the oldest single-core Intel Macs the difference is noticeable; on more recent Mac Pros — notably the current Core i7 “Nehalem” Xeon 8-core/16-thread models — the word “dramatic” has been used more than once.

CPU-specific tweaks and ever more pervasive use of threading as part of the Grand Central optimization project are a significant part of the reasons for the difference; but the one area where 10A335 really shows off its growing muscle is OpenCL.

As many readers already know, OpenCL is Apple’s implementation of GPU co-processing; that is, tapping the huge computational power of the graphics processor for general-computing tasks. In previous builds of Snow Leopard, OpenCL was present and delivered impressive results for certain tasks….but over the past month, the benefits of the technology have become considerably more pervasive.

In tasks which have the most obvious potential for being accelerated by OpenCL such as video encoding, 10A335 is upwards of 10-15% faster than previous seeds, suggesting that the core of the technology has been improved — but via a nifty little internal tool called “OpenCL Monitor,” sources at Infinite Loop have allowed Rumors to see just how active the GPU is when undertaking common everyday tasks in Snow Leopard such as web browsing in Safari 4 or Firefox 3.1b3, reading/viewing email in, using any one of several Twitter applications, or even listening to music with iTunes or Pandora.

Compared with previous seeds, OpenCL was much more heavily involved in accelerating these tasks; also, when both audio and complex 3D graphics (for example, iTunes Visualizers or playing games while listening to Pandora) or other mixed-media tasks were undertaken simultaneously….the amount of CPU used is much lower than with Mac OS X 10.5.x or even Snow Leopard 10A314, and the framerates/performance of the tasks were markedly improved. Multi-tasking while running such applications in the background is considerably snappier.

Performance improvements are to be expected at this stage, since Snow Leopard is still technically in the “alpha” phase and is only just beginning to approach true “beta” status….but what really struck our sources and hands-on reporters is the remarkable stability of 10A335.

The previous build, 314, was many things but it was far from stable. We’ve received several bug reports (many of them quite nasty crashes, more extreme than typically seen with a build of OS X at this point in its developmental life cycle) from developers every single day this month that 10A314 was in the wild as the current dev-seed.

Since 335 was released last Wednesday, we’ve only received two(!). Both involving strange errors being spit out by the OS during the shut-down process, causing delays in shutdowns or reboots, but no bona-fide crashes.

That isn’t to say that 335 is rock-solid stable; we’ve managed to make a few bundled applications including QuicktimeX Player and iTunes crash in our own hands-on testing over the weekend, but even in our most intense stress-tests thus far we haven’t been able to make the system itself lock up.

Some testers reported than the previous build, 314, was somewhat slower than its predecessors….most likely due to the debug code which was removed in 335. So some of the perceived performance difference could be simply due to the nature of the development process; but other things, including the size of applications (both on disk and in RAM), have clearly changed in the past month — and very much for the better.

Boot-up times are subtly improved, the system itself uses approximately 10% less RAM (depending on how much is present on a given system), and I/O from all storage devices — particularly slower ones — is noticeably smoother due to improved memory caching routines.

Given the state of the new build, and the continued absence of several key features which Apple is keeping tightly under wraps until late in the “beta” stage, some on the grapevine have speculated that Snow Leopard might not meet its original June (WWDC) release target.

According to the best information our sources can provide — which we consider very reliable, but Apple has plenty of time to change its course/mind between now and the World Wide Developer Conference (June 8-12th) — this is the not the case. Even if it requires cutting features or holding them back for 10.6.1 et cetera….Infinite Loop *will* hit its targeted shipping date.

That said, there is no hard & fast reason why Mac OS X 10.6 would have to actually ship on June 8th to meet that target. As long as a finalized “Golden Master” build is delivered to developers at WWDC, the actual boxed discs could ship as late as the last week of June and still fulfill last year’s promise of “About a Year From Now.”

Other speculation has centered around Snow Leopard’s expected pricing — the traditional $129 of previous major releases, or something lesser to encourage adoption in tough economic times — but that’s a topic for another day. Clarity is still a moving target on this subject because according to sources, even Apple is still debating this internally.

Stay tuned for much more in-depth, hands-on reporting of testers’ experiences with this latest build of Infinite Loop’s next-generation operating system and its little cousin “iPhone OS” 3.0 in the days to come! If you want exclusive details and insights that go beyond our blog postings, don’t forget to Follow us on Twitter — and we’re always excited to hear from you: whether it’s by email, IM (AIM/iChat: MacOSRumors), or by simply submitting a comment using the form below!

Share this post: Share this article on Facebook Share this Article on Twitter Add this Article to Stumbleupon Add this Article to Add this Article to Digg Add this Article to Reddit Add this Article to Newsvine
This entry was posted in Apple Software and tagged , , , , , , , , , , , , , , , , , , , , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.
  • ryan

    Just a minor addition, the bug fix listing from the 10A335 seed notes:

    *Migrating users over a network connection may result in a hang. Connect the machines via Firewire to workaround this.

    *It may take several minutes to get to the Mac OS X Installer when using a DVD.

    *Some settings such as Mobile Me login info and Keyboard settings are not migrated correctly.

    *Some Rosetta applications crash on launch.

    *‘Repair Permissions’ in Disk Utility reports spurious errors.

    *configd crashes can cause DNS lookups to fail.

    *Custom install sizes are sometimes inaccurate, which may result in the Install Assistant failing due to disk space issues.

    *Quicktime Player X may crash when playing DRM protected content in 64-bit.

    *PowerPC apps are crashing for some users after installing Rosetta. Running ’sudo update_dyld_shared_cache’ in Terminal and then rebooting will typically work around this. Note that you will be prompted for your admin password.

  • Rob

    But how much faster wrt tiger or leopard (which is slower than tiger, though)?

  • captain kid

    i dont know about any one else but one simple under the hood feature i would like to see is an \e mail file\ option when i right click something.

  • Edd

    Pricing: Apple has never really strayed from $129 as the “magic price point” so why change now? Apple has costs to cover and $129 seems to have always been the price of admission. Recession means nothing to Jobs & company.

  • Steve H

    If anyone from Apple/Snow Leopard development is monitoring this thread… There’s a lot of buzz about stability, but I hope the following things are fixed (which occur in Leopard 10.5.6) –

    1) Burning a backup DVD via Burn Folders (Finder) – The Finder often resets after clicking “burn” for a DVD via a Burn Folder – all open windows disappear and the Burn Folder becomes “locked” – On an annoyance scale of 1-10 (10 worst), this is a 5

    2) Setting global folder preferences (Finder) – Can someone please add a way to set global finder window defaults that stick and are truly global. So I (for example) can set ALL windows to “list view” (Command 2), and all new windows to have that setting. On my annoyance scale, this is an 11, maybe a 12.

    Right now, I have to go through nine (9) steps to set them up the way I want them, when I create a new directory:

    (starting in the Finder)
    a) Command-Shift-N for New Folder
    b) Command-Shift-T to hide the navigation bar on the left (which I dislike)
    c) Command-2 to view the contents in “List view”
    d) Command-J to display the folder’s “view options”
    e) Check “Always open in List View”
    f) Uncheck “use relative dates”
    g) Check “calculate all sizes”
    h) Click “use as defaults”
    i) Lather, Rinse, Repeat (because these settings never stick)

    In other words – I want to set these preferences (or any preferences) just ONCE, and have them take effect globally, for every folder on the computer. Isn’t that what the “Use as Defaults” button at the bottom of the view options window is for?

    3) Microsoft Office 2004 (current dot release and previous) often crashes. I remember reading that something about Apple no longer licensing some O/S technology (can’t remember which) to Microsoft…

  • Josh

    captain kid, this would actually be fairly simple if you wanted to design one yourself. I’m not fluent by any means in apple script or whatever language it would require to make what you’re referring to, which is known as a Contextual Menu Item, but I’m fairly certain that with a bit of googling you could either acquire the skills to make one, or find something like this that already exists. Simply in terms of logistics, the code would probably simply involve retrieving the file path of the file you’re right clicking on, opening mail (easy with apple script), opening a new email (also done with apple script), and attaching the given file path, which shouldn’t be too difficult. I’d say you should try it if you have a bit of free time. It’d be an interesting challenge