Two-way invoke thread pool is limited

Bug #1360281 reported by Marcus Tomlinson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-scopes-api (Ubuntu)
New
Wishlist
Unassigned

Bug Description

In ZmqMiddleware::start() we assign the size of twoway_invokers_ to 8 which can at most handle 5 layers in a scope aggregating hierarchy. I'm sure this is fine for 99% of scopes but we still run the risk of hitting this limit because... well... its limited.

Perhaps we could redesign our thread pool class to maintain a minimum number of threads that we spin up on creation, then allow for it to grow if all are busy and another job arrives?

Just a suggestion. We can discuss this further when we have some time.

Changed in unity-scopes-api:
importance: Undecided → Wishlist
affects: unity-scopes-api → unity-scopes-api (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.