Sometimes, a busy-wait situation is your only option. Other times, perhaps it's time for a code refactor ? Trading responsiveness for less CPU load can be a pain in the butt . . .
On Wed, Oct 14, 2015 at 10:30 AM, 'Barry Day' via BeagleBoard < beagleboard@googlegroups.com> wrote: > It's not something I would recommend but on the other hand I've got a bbb > in a cabinet in an industrial shed running at near 100% cpu usage 24/7 and > has been for about a couple of months. I haven't noticed it getting warm > and it's still working fine. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
