Project

General

Profile

Bug #17921

Planning of remote execution task on large number of hosts (reported with 500 hosts) takes a lot of time, potentially leading to stuck task

Added by Ivan Necas over 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

With large amount of hosts, it seems the way we resolve the targeting is sub-optimal,
leading planning to take too much time.

We should revisit the resolving algorithm https://github.com/theforeman/foreman_remote_execution/blob/v1.2.2/app/models/targeting.rb#L41 to optimize it, probably by not loading the
whole host objects.

Similarly, we should revisit also the job invocation phase to make
sure we don't load all host objects at once https://github.com/theforeman/foreman_remote_execution/blob/v1.2.2/app/lib/actions/remote_execution/run_hosts_job.rb#L30

Associated revisions

Revision c44017f0 (diff)
Added by Shimon Shtein over 5 years ago

Fixes #17921 - optimized task queries

Task queries were optimized for not bringing too much unneeded
objects. For more optimizations a proper performance analysis
is needed

History

#1 Updated by Ivan Necas over 5 years ago

  • Subject changed from Planning of remote execution task on large number of hosts (reported with 500 hosts) takes a lot of time, potentially leading to stuck task to Planning of remote execution task on large number of hosts (reported with 500 hosts) takes a lot of time, potentially leading to stuck task
  • Target version set to 1.11.1

#2 Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Shimon Shtein
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/222 added

#3 Updated by Shimon Shtein over 5 years ago

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

Also available in: Atom PDF