> > On 11 May 2011, at 18:48, kxng wrote: > > > Here are the results I ran your sample program on one core and = > dualcore machines: > >=20 > > One Core: > > run with Update Less: Worker0: on average takes 3750 miliseconds > > Worker0 + Worker1: on average takes 5980 ms > >=20 > > Dual Core: > > run with Update Less: Worker0: on average takes 4000 ms > > Worker0 + Worker1: on average takes 7532 ms. > >=20 > > I looked at the task manager performance when running on dualcore, the = > two cores were not processing simultaneously. > >=20 > > I would like to take the advantage of the dualcore. What is the = > approach I should take to program one core doing calculation while the = > other core displaying results? > > OK - on this Quad-core Mac, I took the code, added a few more threads = > (for 4 in total) and raised GUI_REFRESH_THD to 987654, and that was = > enough to peg all 4 cores, whilst the GUI remained responsive. > > So that surely must also work for you. > > > > >
What is the running time of 4 threads compared to one thread? I am interested in knowing if all threads actually running concurrently on 4 cores, because running it on a dualcore machine, the running time does not tell me that is the case. Thanks, _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
