This post, and the posts referred to in it, are VITAL reads for those of you who are "spec" watching, to decide on what will perform well, and won't, theoretically.
Originally Posted by gbp
Dual core technology is important for heavy simultaneous computing - desktop computers can have as many as 100 processes running in the background at the same time. Don't believe me? Use the Task manager and see for yourself!
Before dual processors came along, those processes slowed the single core CPU down, and people complained about performance.
With smartphones, EvilKell is so on target, its not even close to being an agrument - you cant double the speed of the smartphone with mutiple cores, but, you can benefit from havingboth cores processing information at the same time, IF the code of the OS and the application allows it.
Ive spoken to a very experienced computer scientist about what it means to "optimize" code for dual core processing, and you know what he told me?
He said it was making sure that data structures that were being accessed by more than one call from the system or an application were handled correctly in order to reduce system inefficiency. If you are trying to access, an change a data structure at the same time others are doing the same thing, this is a big problem - so, this is where that optimization comes into play - it reduces issues by providing prioritization protocol for such instances, on an instance level basis.
So, optimization for dual core doesn't "increase" the speed of the OS, but, rather assures that it can run efficiently.
Having disclosed the above, a single core device doesnt have to be optimized, as it is already prioritized to handle such events.
HP made a good decision going with the single core 1.4 ghz CPU, IMO - the ONLY mistake they made, I believe, was not going with more RAM - 512 mb is (and I could be wrong, but, I don't think so) too small for an OS like WebOS, that is built and designed to have many user-initiated applications (cards) open at the same time, and left open - that can be a performance issue relative to the amount of RAM each open app takes up - they should have recognized this, IMO, and put 1G or more of RAM in there.