Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1519342 - Persisted sqlite on smart proxy for remote execution is too slow for remote execution at scale
Summary: Persisted sqlite on smart proxy for remote execution is too slow for remote e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
: 1416542 (view as bug list)
Depends On: 1416542
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-30 15:49 UTC by Ivan Necas
Modified: 2021-06-10 13:46 UTC (History)
17 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_dynflow_core-0.1.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1416542
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rex_times.dat (253 bytes, text/plain)
2018-01-08 18:42 UTC, Roman Plevka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20626 0 Normal Closed Provide a way for automatic cleanup of old execution plans from dynflow (especially useful on smart-proxy) 2020-01-15 12:20:58 UTC
Foreman Issue Tracker 20721 0 Normal Closed Use in-memory squite for smart_proxy_dynflow 2020-01-15 12:20:58 UTC

Comment 2 Ivan Necas 2018-01-02 19:29:01 UTC
*** Bug 1416542 has been marked as a duplicate of this bug. ***

Comment 3 Roman Plevka 2018-01-08 18:40:53 UTC
VERIFIED on sat6.3.0-30

- verified that the configuration is set to use the in-memory db
- performed and measured times of `date` command execution on {1..10001} hosts:


Y-axis refers to time in seconds:

                              REX job exeution time                           
                                                                               
  1000 +-+-----------+------------+-------------+------------+-----------+-A   
       +             +            +             +            +             +   
   900 +-+                                          execution time  A A  +-+   
   800 +-+                                                               +-+   
       |                                                     A             |   
   700 +-+                                             A                 +-+   
       |                                                                   |   
   600 +-+                                      A                        +-+   
   500 +-+                                                               +-+   
       |                                 A                                 |   
   400 +-+                                                               +-+   
       |                          A                                        |   
   300 +-+                 A                                             +-+   
       |                                                                   |   
   200 +-+           A                                                   +-+   
   100 +-+    A                                                          +-+   
       +             +            +             +            +             +   
     0 AEX jobe exeution time-----+-------------+------------+-----------+-+   
       0            200          400           600          800           1000 
                                     hosts (#)                                 


Planning times seem to be sane as well now:


                             REX job planning times                            
                                                                               
  3.5 +-+-----------+-------------+------------+-------------+-----------+-+   
      +             +             +            +             +             A   
    3 +-+                                            planningAtime    A  +-+   
      |                                                             A      |   
      |                                                                    |   
  2.5 +-+                                A            A                  +-+   
      |                                                                    |   
    2 +-+                                      A                         +-+   
      |                                                                    |   
      |                                                                    |   
  1.5 +-+                         A                                      +-+   
      |                                                                    |   
    1 +-+           A      A                                             +-+   
      |                                                                    |   
      |                                                                    |   
  0.5 +-+    A                                                           +-+   
      +             +             +            +             +             +   
    0 AEX jobe exeution time------+------------+-------------+-----------+-+   
      0            200           400          600           800           1000 
                                    hosts (#)                                  
                                     


I also tried to run the above on 10k hosts (10001):
execution time: 11098
planning time:  76.21

(attaching the complete dataset as rex_times.csv)

used script (server side):

for i in {0..1000..100}; do
  HOSTS=`awk -F "," '{print $2","}' fero_hosts | head -n $i`
  printf "$i\t" >> times.csv
  /usr/bin/time --output time.txt -f "%e" hammer job-invocation create --inputs "command=date" --search-query="name ^ (${HOSTS})" --job-template-id=107
  cat time.txt >> times.csv
  echo "" > time.txt
done

Comment 4 Roman Plevka 2018-01-08 18:42:15 UTC
Created attachment 1378663 [details]
rex_times.dat

Comment 5 Satellite Program 2018-02-21 16:54:37 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, 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-2018:0336


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