Bug 1473263

Summary:	Processing outputs of remote command on the smart-proxy is slow.
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Unspecified	CC:	aruzicka, inecas, jcallaha, pcreech, vijsingh
Target Milestone:	6.11.0	Keywords:	Performance, Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-smart_proxy_dynflow-0.6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:27:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Ruzicka 2017-07-20 10:47:22 UTC

Description of problem:
When running jobs on large number of hosts, slow checking of outputs can have severe impact on execution time of the entire job.


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


How reproducible:


Steps to Reproduce:
1. Run a job on 1k hosts outputting a single character each second for five minutes.
2. Run a job on 1k hosts outputting a single character into a temporary file each second for five minutes and reading it whole at the end.

Actual results:
The first job is by orders of magnitude slower than the second one.


Expected results:
The two jobs should take roughly the same amount of time to finish.


Additional info:
Job #1: 15:22:43 - 16:43:24 (almost hour and a half)
Job #2: 18:09:38 - 18:23:40 (roughly 15 minutes)

Comment 1 Adam Ruzicka 2017-07-20 11:01:31 UTC

Created redmine issue http://projects.theforeman.org/issues/20362 from this bug

Comment 3 Bryan Kearney 2018-09-04 17:46:25 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 4 Adam Ruzicka 2021-07-20 09:38:37 UTC

We actually have fixes ready now, reopening.

Comment 6 Bryan Kearney 2021-11-11 16:00:54 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32565 has been resolved.

Comment 7 Peter Ondrejka 2022-01-18 13:57:49 UTC

Checked on Satellite 7.0 snap 5, verified that the code pieces landed as expected

Comment 10 errata-xmlrpc 2022-07-05 14:27:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498