#1231 optimize max-builds feature
Closed: Fixed 3 years ago by praiskup. Opened 4 years ago by praiskup.


We should consider calling "update" (frontend api) form action worker, instead of dispatcher, if possible. It takes some time to mark something is done....

Currently we have throughput ~40 actions per minute, which is terribly slow (considering that the action does only directory removal).

We should consider calling "update" (frontend api) form action worker, instead of dispatcher, if possible. It takes some time to mark something is done....

Currently we have throughput ~40 actions per minute, which is terribly slow (considering that the action does only directory removal).

Work-around was to set:

sleeptime=100
actions_max_workers=150

And hack /bin/copr-repo so it doesn't run createrepo_c/modifyrepo_c in affected
project. That allowed us to process the queue without causing further inconsistencies.

Screenshot_20200124_081526.png

Metadata Update from @praiskup:
- Issue priority set to: High

4 years ago

Metadata Update from @praiskup:
- Issue untagged with: RFE
- Issue tagged with: bug

4 years ago

Re-flagging as bug. We will have "priority" for actions, so we should set very low priority for those actions.

Priorities for actions are in production!

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Attachments 2