[Python-ideas] Add an introspection API to Executor

[Dan O'Reilly]

I'll take a look at this again tonight and see if more detailed information
(e.g. which tasks are actually being processed) can be determined without
too much added complexity and/or performance penalties. If I can come up
with something reasonable for both ProcessPool/ThreadPool, I'll add it to
the changes I've already made. Either way, I'll create an issue to track
this.


On Mon, Aug 25, 2014 at 2:54 PM, Guido van Rossum <guido at python.org> wrote:

> It might be worth it to make the implementation somewhat more complicated
> if it serves a good purpose, for example giving the user of the program
> insights into how well the executor is performing. Without such insight you
> may be attempting to tune parameters (like the pool size) without being
> able to evaluate their effect.
>
>
> On Mon, Aug 25, 2014 at 11:43 AM, Antoine Pitrou <antoine at python.org>
> wrote:
>
>> Le 25/08/2014 14:16, Ram Rachum a écrit :
>>
>>  Maybe I'm missing something, but I don't think that's something that
>>> should block implementation.
>>>
>>> Information not available? Change the executor code to make that
>>> information available.
>>>
>>
>> Not if that would make the implementation much more complicated, or
>> significantly slower.
>>
>>
>> Regards
>>
>> Antoine.
>>
>>
>> _______________________________________________
>> Python-ideas mailing list
>> Python-ideas at python.org
>> https://mail.python.org/mailman/listinfo/python-ideas
>> Code of Conduct: http://python.org/psf/codeofconduct/
>>
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
>
> _______________________________________________
> Python-ideas mailing list
> Python-ideas at python.org
> https://mail.python.org/mailman/listinfo/python-ideas
> Code of Conduct: http://python.org/psf/codeofconduct/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20140825/49ccc851/attachment.html>