Project

General

Profile

Actions
Copy link

Bug #19903

open

Massive slowdown of browser when updating lots of nodes via API

Added by Nicolas CHARLES over 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
-
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
48
Name check:
To do
Fix check:
To do
Regression:

Description

I used the API to update node properties on all nodes, so it triggered about 3500 policy generations requests.

Each of those reseted the state of the turning wheel (saying that the policy generation was starting), and browser got nealy ususable after a while.

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 900 to 7.0.0~beta2
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.0~beta2 to 7.0.0~beta3
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.0~beta3 to 7.0.0~rc1
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.0~rc1 to 7.0.0~rc2
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.0~rc2 to 7.0.0~rc3
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.0~rc3 to 7.0.0
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.0.0 to 7.0.1
Actions
Copy link
 #8

Updated by François ARMAND about 2 years ago

  • Translation missing: en.field_tag_list deleted (Blocks 7.0.0)
  • Subject changed from massive slowdown of browser when triggering thousand of policy generation via API to Massive slowdown of browser when updating lots of nodes via API
  • Description updated (diff)
  • Target version deleted (7.0.1)
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 48

This bug is not specific to 7.0 and will likely need an architecture change.

Possible workaround to try:

- try to use `rudder_generation_delay` settings to delay generation and avoid the behavior
- try to use group node properties to avoid having to change properties on node

Actions
Copy link

Also available in: Atom PDF