> > > And was certainly fit for purpose, only problem is, as=20 > > expected it 'hosed' the CPU ;-> Until I tell it not to run at=20 > > full whack then this is going to happen no matter what the=20 > > spec of the machine I suppose.=20 > > Pegging the CPU to the endstop is seldom an issue, so long as the heavy > thread yields often enough to allow everything else to remain > responsive. > > You have the hardware there, and you are pumping electrons through it > anyway, so you might as well use it all if that's what it takes to get > the job done... That's assuming what you are doing is heavy number > crunching, of course. > > On the other hand, if your calculation only needs to be done at a fixed > rate, maybe you should be looking at Fl::add_timeout() to see about > running updates via a timer? > > > > I have just told the program=20 > > to 'GO' so I think I could afford to cap the framerate (if=20 > > that is accessible in FLTK?) a little and reduce CPU that=20 > > way, but I think the clear answer is really to go with the=20 > > multithreading. > > Even with multiple threads, if your calculation does not need all the > CPU you might want to think about using timers to schedule appropriate > updates and recalculation periods... > > > > > SELEX Galileo Ltd > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS= > 14 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > You have the hardware there, and you are pumping electrons through it anyway, so you might as well use it all if that's what it takes to get the job done... That's assuming what you are doing is heavy number crunching, of course.
..... A good point, the user would just want an optimal result generated, and that costs cpu. And yes, its ideally all needed, to run one test loop alone could take several minutes at top settings, and the only way best result is obtained is running lots of loops, really the app is designed to be started up and as often as not left running for a few hours, maybe longer. So that means user will maybe want to do something else on the machine, so given its runnign for a few hours anyhow, may as well use your suggestion and free a little resource up anyhow _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
