In VMware, ReactOS eats up all available CPU time. Does anyone have an idea why? Does it also do this on real hardware?
Casper
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Rick Parrish Sent: 15. november 2004 19:59 To: ReactOS Development List Subject: Re: [ros-dev] ReactOS eating CPU time
Casper Hornstrup wrote:
<>In VMware, ReactOS eats up all available CPU time. Does
anyone have
an idea why? Does it also do this on real hardware?
Isn't that just the nature of emulation? How else can the guest OS execute idle loops?
When running Linux in VMware, the CPU can be idle.
Casper
Casper Hornstrup wrote:
In VMware, ReactOS eats up all available CPU time. Does anyone have an idea why? Does it also do this on real hardware?
Casper
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
if you're referring to the GUI then it's because the gui eats up a lot of resources. a single mouse move for example causes roughly 1000 lockings of the user handle table, then a bunch of locks for the gdi - not to mention the lower-level stuff in ntoskrnl. I'm working on this issue (especially the gui) in my rewrite branch.
Thomas
if you're referring to the GUI then it's because the gui eats up a lot of resources. a single mouse move for example causes roughly 1000 lockings of the user handle table, then a bunch of locks for the gdi - not to mention the lower-level stuff in ntoskrnl. I'm working on this issue (especially the gui) in my rewrite branch.
Thomas
No, I'm talking about the CPU never being idle.
Casper
For me, vmware need's almost no CPU if reactos is idling in GUI mode, i.e. not moveing the mouse etc. Wintdows 2000, Vmware 4.5.2
No, I'm talking about the CPU never being idle.
Casper
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of michael@fritscher.net Sent: 15. november 2004 20:41 To: ReactOS Development List Subject: RE: [ros-dev] ReactOS eating CPU time
For me, vmware need's almost no CPU if reactos is idling in GUI mode, i.e. not moveing the mouse etc. Wintdows 2000, Vmware 4.5.2
Hmm, maybe it is just my configuration then. VMware 4.0.5 on Windows Server 2003.
Casper
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Casper Hornstrup wrote: | | | |>-----Original Message----- |>From: ros-dev-bounces@reactos.com |>[mailto:ros-dev-bounces@reactos.com] On Behalf Of |>michael@fritscher.net |>Sent: 15. november 2004 20:41 |>To: ReactOS Development List |>Subject: RE: [ros-dev] ReactOS eating CPU time |> |>For me, vmware need's almost no CPU if reactos is idling in |>GUI mode, i.e. |>not moveing the mouse etc. |>Wintdows 2000, Vmware 4.5.2 | | | Hmm, maybe it is just my configuration then. VMware 4.0.5 on Windows Server 2003. | | Casper
Just to inform, that is an OLD version of VMware, the newer ones may fix some internal error, or do things faster?
~ -uniQ
Casper Hornstrup wrote:
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of michael@fritscher.net Sent: 15. november 2004 20:41 To: ReactOS Development List Subject: RE: [ros-dev] ReactOS eating CPU time
For me, vmware need's almost no CPU if reactos is idling in GUI mode, i.e. not moveing the mouse etc. Wintdows 2000, Vmware 4.5.2
Hmm, maybe it is just my configuration then. VMware 4.0.5 on Windows Server 2003.
Casper
Dont beleave that one moment! I can repeat the slow down on Qemu as well. Just run it for 12+ hours and you will see. James
if you're referring to the GUI then it's because the gui eats up a lot of resources. a single mouse move for example causes roughly 1000 lockings of the user handle table, then a bunch of locks for the gdi - not to mention the lower-level stuff in ntoskrnl. I'm working on this issue (especially the gui) in my rewrite branch.
It's not just the gui. Ros is slow in general also. When compiling ros on ros in native console (in vmware) it takes hours... Ros has long way to go before its as fast as nt 4.
Thomas _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Well....NT4 is a speed demon, so that's not really a fair comparison :D
Gunnar Dalsnes wrote:
if you're referring to the GUI then it's because the gui eats up a lot of resources. a single mouse move for example causes roughly 1000 lockings of the user handle table, then a bunch of locks for the gdi - not to mention the lower-level stuff in ntoskrnl. I'm working on this issue (especially the gui) in my rewrite branch.
It's not just the gui. Ros is slow in general also. When compiling ros on ros in native console (in vmware) it takes hours... Ros has long way to go before its as fast as nt 4.
Thomas _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Is ros just sitting idle? Ros is pretty well behaved here on VMWare, but the new networking code with all the messages it spits out keeps the host cpu pretty busy.
On Mon, 15 Nov 2004 19:48:56 +0100, Casper Hornstrup chorns@users.sourceforge.net wrote:
In VMware, ReactOS eats up all available CPU time. Does anyone have an idea why? Does it also do this on real hardware?
Casper
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Hi! Casper Hornstrup wrote:
In VMware, ReactOS eats up all available CPU time. Does anyone have an idea why? Does it also do this on real hardware?
Casper
Yes, real hardware! It's the GUI! Explorer! I can run ROS for one week in cmd only mode, compile and so on! But, when in the GUI, it slows down! So slow you can watch the char's type across the cmd window.
It good to see others haven the same problem I've been writing about for months now! James
Yes, real hardware! It's the GUI! Explorer! I can run ROS for one week in cmd only mode, compile and so on! But, when in the GUI, it slows down! So slow you can watch the char's type across the cmd window.
It good to see others haven the same problem I've been writing about for months now! James
I'm pretty sure my problem is not the same. I don't boot into GUI and I let ReactOS be idle for a while and the VMware monitor still use all CPU time. With Linux it does the same until a few seconds after leaving GRUB. Then CPU usage varies until Linux is idle and yhen CPU usage is almost zero. I suspect maybe it is due to Linux utilizing power management and VMware recognizes it or something like that.
Casper
----- Original Message ----- From: Casper Hornstrup To: 'ReactOS Development List' Sent: Tuesday, November 16, 2004 8:57 PM Subject: RE: [ros-dev] ReactOS eating CPU time
I'm pretty sure my problem is not the same. I don't boot into GUI and I let ReactOS be idle for a while and the VMware monitor still use all CPU time. With Linux it does the same until a few seconds after leaving GRUB. Then CPU usage varies until Linux is idle and yhen CPU usage is almost zero. I suspect maybe it is due to Linux utilizing power management and VMware recognizes it or something like that.
Casper
Hi
I'm also on Windows 2003 Server and I do not have this problem. When ReactOS is idle, VMware takes 0% CPU. I have configured the guest OS as WindowsNT, do you have any other setting? I'm running VMWare 4.5.2... Like K McI said, maybe you should try updating.
/Andreas Bjerkeholt