[Touch HD Windows Mobile ROM Development] daeron.be:
It's called placebo effect and well, it matters. Roms are cooked for people to use and in my opinion, people will use rom they "feel" is faster anyway. Starting this thread I wanted to show people some more "reliable" results and show them which roms should feel "fast" - because they are really fast. And yeah, I am well aware of fact, that those tests would be much more reliable if they were checking performance on things people really use - for exaple manila speed, time to run a their favorite programs, boot time etc. My (well, Houms is doing almost whole job right now ;P) test shows performance of opengl, time of copying one big file or writing or reading many small files, listing files in a directory, 2d "arkaball" performance or CPU tests I'm trying to check overall performance of some rom with best tools I have. In theory, if a rom scores good in those benchmarks, it should run almost everything well. But as you can see, there isn't much difference - 20% isn't really that much. Most people probably won't see much difference if they won't have 2 Blackstones in they hands running for example "Topaz vanilla final 2009.06.13" and "PhamQuang 6.5 v40" roms. But hey, that would be a neat test! :P If somebody have 2 Blackstones, please check this out ;)

Guys, I'm not a cook myself but I guess I know how Windows and other OSes run, I surely say, that "numer" of apps installed itself doesn't influence speed of rom. What influence, then?

- executables (*.exe) and libraries (*.dll) running in a background and foreground :) - they eat ram, and often then they're in 'active' state they use cpu time.

- disc fragmentation - but I don't think it has much influence here

- software (OS and third-party apps) - their "quality". It's obvious - with poor graphics drivers that doesn't support direct rendering or they do it poorly you won't play 3d games. Even if you run them it won't be a game :).

- configuration of software changes the way software behaves - changing cache sizes e.g.

Cookers work with OS and third-party apps installed in a rom, they change configurations, use different parts of the system... It's like making a car, and they have quite a few cars already made, and cooks can get parts from everyone of them and create a new car - rom we say. They can create parts by themselves, but in a limited way, because Microsoft doesn't provide sources - it's not GNU/Linux - it's f@#$%^& proprietary software, and - forgive me, Cooks - rom makers doesn't create almost anything new, they only use parts of other roms. But they can't do anything else, without reverse-engineering, which is pain-in-the-ass. I respect rom cookers, but i respect people working on porting Android into Blackstone even more.

And look. Both Light and Big Kwbr's roms are at the top of the list (they have more than 92%) - Dutty's is here too even though it's a 'big' rom.

If you ask me to separate 6.1 and 6.5 show me any differences between them - they are the same as between some 6.1 roms - they have other gui and their performance varies - according to my (Houms? ;p) test.

And 6.5 roms shouldn't be treated specially. Tests show that they are much slower. That's all.

I feel like I wrote a longest text in English ever. Huh.

And wow, I feel honored, I really loved your roms - DuttyThroy and Laurentius26 - before I've seen Kwbr's. But I'm cheering on you anyway :)

BTW: There're another 3 benchmarks by Houms.

Yay, JohnPatcher, congratz on your newest Barebone ;) It's in very top :) 0.13% is like no difference. :)