Bug 1388266 - Koji integration: instead of using a thread pool we need a better asyncio aware integration
Summary: Koji integration: instead of using a thread pool we need a better asyncio awa...
Keywords:
Status: MODIFIED
Alias: None
Product: rpm-test-trigger
Classification: Community
Component: general
Version: unreleased
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard:
Depends On: 1388265
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-24 23:27 UTC by Roman Joost
Modified: 2018-11-09 23:17 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Roman Joost 2016-10-24 23:27:53 UTC
The current koji integration uses the koji Python client package. The downside of it is that we're using a threadpool to execute the koji requests to XMLRPC concurrently. This can be expensive and won't scale more than what we're bound by the CPU of the host machine.

Alternatives:

* Don't use a thread pool and the koji client library, but instead use the requests solution from Bug 1388265
* Write your own XMLRPC asyncio library??

Comment 1 Dan Callaghan 2016-12-09 06:16:19 UTC
https://gerrit.beaker-project.org/5531


Note You need to log in before you can comment on or make changes to this bug.