yahoo-eng-team team mailing list archive

[Yves-Gwenael Bourhis <yves-gwenael.bourhis@xxxxxxxxxx>]

Public bug reported:

When looking at the keypair dashboard, or router dashboard, etc...
openstack_dashboard.usage.quotas.tenant_quota_usages queries also
cinder, etc... and therefore makes tons of unused and unnecessary api
calls.

It slows down panels very heavily.

I did a quick and dirty test on some dashboards (with a local horizon
targeted on a production environment's APIs) by modifying the
tenant_quota_usages function to retrieve only the desired quotas and
usages for the page I need, and it turns out that rendering a page is
between 3 to five time faster. Just enormous.

We really do not need to fetch all usages and quotas when retrieving
keypairs, etc...

This function should accept extra parameters to get only the desired
quotas and usages.

However this is a huge task because it requires modifying ALL
dashboards.

But quick tests show that the performance impact is simply more than
tremendously gigantic. e.g.: My "routers" page with the current function
takes 20 to 30 seconds to render (just catastrophic), and only 3 to 5
seconds If I get only the the desired quotas and usages.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1675504

Title:
  openstack_dashboard.usage.quotas.tenant_quota_usages fetches to many
  quotas and degrades performances

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When looking at the keypair dashboard, or router dashboard, etc...
  openstack_dashboard.usage.quotas.tenant_quota_usages queries also
  cinder, etc... and therefore makes tons of unused and unnecessary api
  calls.

  It slows down panels very heavily.

  I did a quick and dirty test on some dashboards (with a local horizon
  targeted on a production environment's APIs) by modifying the
  tenant_quota_usages function to retrieve only the desired quotas and
  usages for the page I need, and it turns out that rendering a page is
  between 3 to five time faster. Just enormous.

  We really do not need to fetch all usages and quotas when retrieving
  keypairs, etc...

  This function should accept extra parameters to get only the desired
  quotas and usages.

  However this is a huge task because it requires modifying ALL
  dashboards.

  But quick tests show that the performance impact is simply more than
  tremendously gigantic. e.g.: My "routers" page with the current
  function takes 20 to 30 seconds to render (just catastrophic), and
  only 3 to 5 seconds If I get only the the desired quotas and usages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1675504/+subscriptions