OOOOkay... took me some time to figure out what was going on since I was looking for a bug in my code and it was actually a feature in openMP
The good news. this is a feature. To optimize perfs, openmp will have all its threads busy-wait when no job is available on the assumption that it's a rare occurence. This explain teh CPU usage setting the environment variable OMP_WAIT_POLICY=PASSIVE will solve the problem the bad news... I was not to set it within the code. Adding a call to setenv as the first instruction of main() didn't work since env variables seem to be loaded in OMP context even before that. I couldn't find a way to set it and i'm open to suggestions here... Regards Boucman On Fri, Apr 1, 2011 at 2:57 PM, jeremy rosen <[email protected]> wrote: > Ok, I can confirm the problem, I'll try to see what's going on with > some tracing... > > On Thu, Mar 31, 2011 at 6:31 PM, Ignacio Riquelme Morelle > <[email protected]> wrote: >> On Thursday 31 March 2011 08:19:45 Karol Nowak wrote: >>> Did you have, by any chance, terrain animation turned on? >> >> No. As I said later, I disabled all sorts of animations for testing. >> >> -- >> Regards >> Ignacio Riquelme Morelle <shadowmaster> >> >> _______________________________________________ >> Wesnoth-dev mailing list >> [email protected] >> https://mail.gna.org/listinfo/wesnoth-dev >> >> > _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
