Project

General

Profile

Actions

Bug #20182

closed

High CPU load and slow response times on the smart proxy (smart_proxy_dynflow_core process) with rex at scale

Added by Adam Ruzicka almost 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1463506

Description of problem:
Due to inefficiency of the refreshing of execution, smart_proxy_dynflow_core can
get under heavy CPU load, which can eventually lead to slow response times
and bloated queues.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run remote execution job against 1000 hosts

Actual results:
smart_proxy_dynflow_core getting to 100% CPU soon, response times
on smart_proxy getting to tens of seconds

Expected results:
Moderate CPU load, fast reponse times on smart-proxy (below second)

Additional info:
Extracted from https://bugzilla.redhat.com/show_bug.cgi?id=1416542#c36 to have more clarity on different parts of the bug.


Related issues 1 (0 open1 closed)

Related to foreman-tasks - Bug #20273: Timeout support in foreman-tasks is brokenClosedAdam Ruzicka07/11/2017Actions
Actions #1

Updated by Adam Ruzicka almost 7 years ago

  • Project changed from Foreman Remote Execution to foreman-tasks
Actions #2

Updated by The Foreman Bot almost 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-tasks/pull/262 added
Actions #3

Updated by Anonymous almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Ivan Necas almost 7 years ago

  • Related to Bug #20273: Timeout support in foreman-tasks is broken added
Actions #5

Updated by Ivan Necas almost 7 years ago

  • translation missing: en.field_release set to 278
Actions

Also available in: Atom PDF