2010/1/27 lembas <[email protected]>: > I have Ubuntu 9.04 and Windows XP on Virtualbox on the same machine. > I have dev versions of chrome on both systems. > > For "Chrome 4.0.302.2 dev" on ubuntu test result is > Score: 4741 > Richards: 3956 > DeltaBlue: 4380 > Crypto: 3205 > RayTrace: 5633 > EarleyBoyer: 13652 > RegExp: 1485 > Splay: 8488 > > For "Chrome 4.0.302.3 unknown" on windows xp in virtualbox: > Score: 17593 > > Richards: 13480 > > DeltaBlue: 17520 > > Crypto: 13543 > > RayTrace: 19959 > > EarleyBoyer: 52880 > > RegExp: 5326 > > Splay: 29009 > > Windows is nearly 4x faster even in virtualbox.
If these scores are real you have a system from the future! I think it is more likely that there is a bug in the current-time functions on the virtualbox-hosted Windows system, which causes the elapsed time to be underestimated. This will give you overestimated speeds on the V8 benchmark suite. > > Has anyone done a similar test? > > On Jan 26, 2:13 pm, Erik Corry <[email protected]> wrote: >> 2010/1/26 lembas <[email protected]>: >> >> > Test both google chrome for windows and for linux on v8.googlecode.com/ >> > svn/data/benchmarks/current/run.html. Windows version is much faster. >> >> > why? is it because of the compilers? >> >> There are lots of reasons why this might be. One is that your power >> saving settings may be different in the two OSs. One is that Google >> Chrome on Linux is normally 64 bit whereas Google Chrome on Windows is >> normally 32bit. >> >> How big a difference are you seeing? >> >> -- >> Erik Corry > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
