The i5 is better for compiling code, I would have to agree. My 2500K works well with Visual Studio running C++ and is faster than any of the computers in our computer lab at school...save for maybe the ones with Nvidia cards in them.
Between the two, the i5....I've checked and seen all 4 cores under full load when compiling using Xcode 4.5 on Lion, which means that today's compiler's (or atleast LLVM for that matter) are multi-core optimized
Between the two, the i5....I've checked and seen all 4 cores under full load when compiling using Xcode 4.5 on Lion, which means that today's compiler's (or atleast LLVM for that matter) are multi-core optimized
Code compilers are not multi-threaded. What happens is that the build management software evaluates which object files need re-compile and then issues as many parallel build jobs as there are CPUs but each of these object file jobs are fundamentally single-threaded. Once all object files are built, you are back to waiting on the linker which is usually a single-threaded affair.
That sort of build job parallelizing has been around for decades. Even non-multiprocessor systems still benefited from it since running multiple object builds in parallel lets processes use the CPU while others are stuck waiting on disk IO.
Code compilers are not multi-threaded. What happens is that the build management software evaluates which object files need re-compile and then issues as many parallel build jobs as there are CPUs but each of these object file jobs are fundamentally single-threaded. Once all object files are built, you are back to waiting on the linker which is usually a single-threaded affair.
That sort of build job parallelizing has been around for decades. Even non-multiprocessor systems still benefited from it since running multiple object builds in parallel lets processes use the CPU while others are stuck waiting on disk IO.