Comment 4 for bug 307646
Revision history for this message
| Treeform (starplant) wrote Re: [Bug 307646] Re: lock-to-one-core #f does not work on windows | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I don't think its a Linux bug. I think windows specific because only
on windows there is a problem with the clocking being different for
cores. It will show it to be 50% use that's normal. Look at program
affinity does it use only a single core?
Better experiment start 2 copies of your app. Do they use 100% of cpu
(one to each core) or 50% of cpu ( 25% of cpu each because they are
stuck to one core)
On Sat, Dec 27, 2008 at 11:55 PM, pro-rsoft <email address hidden> wrote:
> Hmm, I can reproduce this bug with ppremake 1.6.0, on Ubuntu Intrepid 64b, with threading disabled, and the config vars correctly set. (I tried both lock-to-one-core and lock-to-one-cpu, which one is the correct one?)
> The system monitor shows just 50% of my processor is in use.
>
> Marked as Confirmed.
>
> ** Changed in: panda3d
> Status: New => Confirmed
>
> --
> lock-to-one-core #f does not work on windows
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>