Yea accept,
1. What you might want to try is use either VM or real hardware, but if you choose something stick to it, (meaning perform the tests for the OS's with same specs) I'm sure you would have done this., am just asking you to double check.
2. GNOME and XP has lot of different start-up services which might affect the test results., SO i would suggest after the initial install of both OS, disable any un-important startup services in both., and restart the test. (When i say services it also includes, disabling any anti-virus blah blah blah)
3. Perform the test in different VM's(VM's by different vendors) possibility is that some vendors custom there optimizations for a particular OS, so by performing the test on different VM's from various vendors we can come at an average time, would lead to a better benchmark.
4. Perform the tests with KDE and XP, coz, that might be a more closer match with XP's startup themes and processes.
5. Then running the test 2-3 times with the above procedures will give a more accurate result, and will also help identify where exactly fedora is slower.
(Am sure your findings are true, but inorder to help developers isolate the problem requires more vigorous testing)
Am sure other people will also be helping in testing simultaneously, which should reduce your burden a bit.
Thanks
Balaji R
On Fri, Mar 28, 2008 at 9:07 AM, Emmanuel Seyman <emmanuel.seyman@xxxxxxxxxxxxxxxx> wrote:
* Dimi Paun [28/03/2008 15:03] :
>> The same must happen here, and the first step is to acknowledge it.The first step is actually to eliminate variables in the test so as
to better isolate the problem. Can you run your test again with the
same platforms on real hardware ? That would eliminate any slowness
due to the virtual setup.
Emmanuel
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
