Project

General

Profile

Actions
Copy link

Bug #15092

open

Queries to fetch changes are too big

Added by Nicolas CHARLES almost 5 years ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
Ideas (not version specific)
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:
0
Name check:
Fix check:
Regression:
No

Description

We are fetching changes by chunk of 6 hours, which is quite slow on large database

On same database, loaded, tests show that:
  • fetching by 6 hours chunks take 324s
  • fetching by 3 hours take 122s * 2
  • fetching by one hours take 28s * 6

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #15041: The computation of changes by rules, at start of web interface, is quite slow ReleasedNicolas CHARLESActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 5 years ago

  • Related to Bug #15041: The computation of changes by rules, at start of web interface, is quite slow added
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #5

Updated by François ARMAND over 4 years ago

  • 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 49

Is this hard to change?

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 49 to 48
Actions
Copy link
 #7

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 48 to 46
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 46 to 44
Actions
Copy link
 #9

Updated by Nicolas CHARLES almost 4 years ago

  • Priority changed from 44 to 43

it is fairly easy to change

Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #13

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #22

Updated by François ARMAND 5 months ago

  • Target version changed from old 6.1 issues to relocate to Ideas (not version specific)
  • Priority changed from 43 to 0
  • Regression set to No
Actions
Copy link

Also available in: Atom PDF