Project

General

Profile

Actions

Bug #47543

closed

mgr/dashboard: fix performance issue when listing large amounts of buckets

Added by Alfonso Martínez over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
Component - RGW
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus nautilus
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Currently we are making 1 request per each bucket (which in backend implies several requests to rgw admin ops api) apart from the bucket list request.

This approach causes a performance issue when the user retrieves large amounts of buckets.


Related issues 3 (0 open3 closed)

Related to Dashboard - Bug #40753: mgr/dashboard: Perform scalability tests with large amounts of RGW bucketsResolvedErnesto Puerta

Actions
Copied to Dashboard - Backport #47618: nautilus: mgr/dashboard: fix performance issue when listing large amounts of bucketsResolvedAlfonso MartínezActions
Copied to Dashboard - Backport #47619: octopus: mgr/dashboard: fix performance issue when listing large amounts of bucketsResolvedAlfonso MartínezActions
Actions #1

Updated by Alfonso Martínez over 3 years ago

  • Related to Bug #40753: mgr/dashboard: Perform scalability tests with large amounts of RGW buckets added
Actions #2

Updated by Alfonso Martínez over 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 37244
Actions #3

Updated by Lenz Grimmer over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47618: nautilus: mgr/dashboard: fix performance issue when listing large amounts of buckets added
Actions #5

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47619: octopus: mgr/dashboard: fix performance issue when listing large amounts of buckets added
Actions #7

Updated by Nathan Cutler over 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions #8

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 143 to Component - RGW
Actions

Also available in: Atom PDF