Re: logging from time critical tasks -- QueueListener().stop() takes the whole CPU

2018-07-15 Thread Gerlando Falauto
On Monday, July 16, 2018 at 8:13:46 AM UTC+2, Thomas Jollans wrote: > On 16/07/18 07:39, Gerlando Falauto wrote: > > On Monday, July 16, 2018 at 6:56:19 AM UTC+2, dieter wrote: > >>> ... > >>> Why is the main thread taking up so much CPU? > >>> I beli

Re: logging from time critical tasks -- QueueListener().stop() takes the whole CPU

2018-07-15 Thread Gerlando Falauto
On Monday, July 16, 2018 at 6:56:19 AM UTC+2, dieter wrote: > > ... > > Why is the main thread taking up so much CPU? > > I believe at this point listener.stop() should only be waiting for the > > helper thread to terminate, which I reckon would be implemented by waiting > > on a semaphore or som

logging from time critical tasks -- QueueListener().stop() takes the whole CPU

2018-07-14 Thread Gerlando Falauto
Hi, I'm adding logging to a time critical task running resource-constrained hardware (Raspberry Pi). I read about the QueueListener/QueueHandler in: https://docs.python.org/3/howto/logging-cookbook.html#dealing-with-handlers-that-block and I'm trying to understand how it really works and what's

Re: array.array()'s memory shared with multiprocessing.Process()

2017-09-12 Thread gerlando . falauto
Il giorno lunedì 11 settembre 2017 12:19:27 UTC+2, Thomas Jollans ha scritto: > On 2017-09-10 23:05, iurly wrote: > > As far as I'm concerned, I'm probably better off using double buffers to > > avoid this kind of issues. > > Thanks a lot for your help! > > > > > That should work. Some other th

Re: array.array()'s memory shared with multiprocessing.Process()

2017-09-10 Thread gerlando . falauto
> > I suspect it's down to timing. > > What you're putting into the queue is a reference to the array, and it's > only some time later that the array itself is pickled and then sent (the > work being done in the 'background'). > > Modifying the array before (or while) it's actually being sent