dbus service thread count about adbus

[charleseidsness]

Hi Lars,

That is sort of expected, but a little surprising. Method calls are run in an executor so that they don't block the mainloop when being processed. This is used to avoid possible deadlocks when method calls call methods on other applications which may call back to us, among other things.

If you don't set the executor (which you can do by passing an argument to the Method init method) it will use the default executor which is a thread-pool.

Python run_in_executor

I would expect that once you hit the maximum threads in your default thread-pool it should start re-using them.

The surprising thing; to me at least, is that it doesn't reuse them as soon as they are available. I guess that's just how it works. We have a lot of test hours on this library and haven't seen massive amounts threads spawned on our systems so I think it's all working correctly, but I will start taking a closer look at it now on our running systems.

Thanks!
Charles

[laped83]

Okay thanks for the feedback. I can also see that you sometime ago has added the ability to use a different executor.

When will you tag a new release? I can also see that https://pypi.org/project/adbus/ is on a v1.0.1.

It will be so easier for me to use a released version when creating an upstreamed rule in the ptxdist(https://www.ptxdist.org/)

Again thanks for the great work!

Regards
Lars Pedersen..

[charleseidsness]

Sure, I just created a new release 1.1.2 and uploaded it to PyPi, or at least I think I did. I have to re-learn how to do it every-time.

[laped83]

Thanks. Looks like you have lost the LICENSE file in the src on pypi?

[charleseidsness]

Thanks! Just updated it with 1.1.3.