I know it is 64bit but just how much faster will this cat be then the Tiger? Will apps like iLife and iWork run faster because of the 64bit-ness? Or will it be like the house of MS and be so heavy it can't run faster... wondering...
A 64 bit OS speeds up processes that work with large files and large amounts of data on 64 bit apps. You might notice Leopard being a bit more snappy, but don't expect too much unless you are doing heavy video, audio or photo editing on optimized programs.I know it is 64bit but just how much faster will this cat be then the Tiger? Will apps like iLife and iWork run faster because of the 64bit-ness? Or will it be like the house of MS and be so heavy it can't run faster... wondering...
My naive hope was that the iWork and iLife 08 DVDs had 64bit versions on them. After all we are not talking about just past versions, this is a 64bit version running on the newest processors, in my case 2.8 iMac; I want if not expect it to scream.Yeah, I don't think you understand 64 bit computing at all. Why would iWork of all things benefit from 64 bit computing?
In the past, new versions of OS X have been slightly faster -- ~5% doing the same task on the same hardware -- than the version they succeed. No one has test data on the release, optimized Leopard yet, but if anything, you'll see it's somewhere between static (no speed difference) and about that much gain. Which is already pretty much better than every other operating system out there.
I appreciate you being kind, but you just sucked all the joy out of my expectations. Well not all, but a lot; ok not a lot but some anyway.Sorry, unfortunately, it is an extremely naïve hope.... you can look at something like this:
Basically, to the extent that the architecture is 64-bit, you can frequently do tricks like moving two 32-bit sets of data simultaneously through a 64-bit bus. But those kinds of tricks usually don't require 64-bit APIs to begin with. There's not necessarily anything about 64-bit processing that will make those kinds of apps "scream." Unless perhaps your spreadsheet in Numbers has 10 gigs of data in it. In which case, one would wonder why you are using Numbers at all instead of industrial class data mining software.
That might be, depending on how they work it. Is iDVD slow even on C2Ds?I would think a 64-bit iDVD would produce a big speed improvement over 32-bit if nothing else. The Professional quality rendering setting takes a lot of CPU power. Moving the data from RAM through the processor in bigger chunks can only help that big time (if Apple have coded it that way).
True that. I really only ever write audio CDs and data discs, so I feel like the whole process has gotten plenty quick for me, but it's good to remember that when it comes to laying down high quality video, the computers could actually use a lot more power.You know how it is, things like rendering can never be fast enough
I would think a 64-bit iDVD would produce a big speed improvement over 32-bit if nothing else. The Professional quality rendering setting takes a lot of CPU power. Moving the data from RAM through the processor in bigger chunks can only help that big time (if Apple have coded it that way).
All of this times 2 with dual processors, right? lol64 bit chips have nothing to do with data load size. The G5, for example, has a 128 bit wide bus, while the G4 has a 64 bit wide bus.
64 bit chips in general change two things only:
1) pointer size. This allows >4GB of memory, but reduces the effectiveness of caches
2) (optionally) integer size. This allows working with numbers larger than 4 billion without breaking them into pieces and doing extra work.
64 bit x86 chips change a few further things:
1) memory addressing is slightly more complex
2) twice as many architected registers are available
3) some old instructions have been removed, breaking compatibility with ancient apps
4) probably a few other minor changes I don't know about
and last but definitely not least, OSX makes a few changes in 64 bit mode:
1) It maps the kernel address space into the first 4 GB of each process, avoiding the need for TLB flushes when making system calls.
2) Certain old APIs (and even some newish ones!) don't exist in 64 bit mode, breaking compatibility with some apps
3) The need for backwards compatibility in many frameworks is gone in 64 bit mode, since there are no 64 bit GUI apps to be backwards compatible with. This lets them revise some things that they couldn't revise before without breaking compatibility, for some nice benefits in certain places.
If it seems complicated that's because it is.