Horizon is very slow in 100 nodes deployment

Bug #1383006 reported by Aleksandr Shaposhnikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
High
MOS Horizon

Bug Description

Very slow horizon UI on 100 nodes cluster.

Please contact MOS-scale team and we will show observed behavior for Horizon. We could just install MOS and provide an access to the environment.
Basically login could take up to 10-20 seconds to complete. Switching between tabs sometimes could be about 30 second but mainly 15-20 seconds.

versions:
api: '1.0'
astute_sha: c3e7c7a18528cf9acca48021488a93dff74f5c97
auth_required: true
build_id: 2014-10-16_19-59-04
build_number: '72'
feature_groups:
- mirantis
fuellib_sha: 677c2809bd602ed6f793b03df49ef8b0f8dcb7e7
fuelmain_sha: 5cf06aac43ccb4a6031fbfa87ff9f9a729314daa
nailgun_sha: b83eaf18cbcc36393f8ac1e7732a6395546a7ca8
ostf_sha: de177931b53fbe9655502b73d03910b8118e25f1
production: docker
release: '6.0'
release_versions:
  2014.2-6.0:
    VERSION:
      api: '1.0'
      astute_sha: c3e7c7a18528cf9acca48021488a93dff74f5c97
      build_id: 2014-10-16_19-59-04
      build_number: '72'
      feature_groups:
      - mirantis
      fuellib_sha: 677c2809bd602ed6f793b03df49ef8b0f8dcb7e7
      fuelmain_sha: 5cf06aac43ccb4a6031fbfa87ff9f9a729314daa
      nailgun_sha: b83eaf18cbcc36393f8ac1e7732a6395546a7ca8
      ostf_sha: de177931b53fbe9655502b73d03910b8118e25f1
      production: docker
      release: '6.0'

Tags: horizon scale
tags: added: scale
Changed in mos:
milestone: none → 6.0
assignee: nobody → MOS Horizon (mos-horizon)
importance: Undecided → High
status: New → Confirmed
tags: added: horizon
Revision history for this message
Timur Sufiev (tsufiev-x) wrote :

I've tested the lab and haven't encountered any extraordinary lags. It took ~6sec from I clicked 'Login' button till the home page of Dashboard has been finally rendered. Switching between different panels took ~2-4 sec, which is also quite usual for Horizon.

That doesn't mean however that everything is perfect in Horizon. I small remark: I am located in Moscow, Russia and the Lab hardware is located somewhere in Czech Republic. I strongly believe that the lags Alexander Shaposhnikov have encountered are related to the big latency he has while sending requests to Czechia.

I've collected debugging info for the successful transition from Login page to the Home page of the dashboard: http://paste2.org/GJ14dzX3 Alexander, could you gather the same logs for the same transition? To do so, you'll need to edit /etc/openstack_dashboard/local_settings.py on all 3 controller nodes, setting DEBUG = True and PROD = False (I don't really know what the latter one means, did it just in case) and restarting apache services on all three. Then see all 3 /var/log/dashboard.log - one of the will receive log messages.

There is another thing I want to notice: somehow the same controller served all my web-requests, which doesn't seem right (why use 3 of them if no load balancing occurs?).

Timur Sufiev (tsufiev-x)
Changed in mos:
status: Confirmed → Incomplete
Revision history for this message
Aleksandr Shaposhnikov (alashai8) wrote :

Timur, It looks that I've seen all the lags because mysql/rabbitmq and affected services(keystone) was overloaded and slowed down.
My main concerns are only about as example those 6 seconds for login. It's quite slow. I wouldn't insist that it should be "fast-as-lightning" but may be you have some ideas how to improve it ? I assume that optionally response shouldn't be more that 3 seconds on any action or it will be out of comfort zone for most of the people.

Revision history for this message
Timur Sufiev (tsufiev-x) wrote :

Aleksandr,

I have an educated guess: the first time the User logs in, Horizon has to evaluate User's permissions for each panel to decide whether it's visible in template or not. Each such evaluation implies REST-request to Keystone or some other OpenStack service. The problem is that these requests are _sequential_, thus different requests latencies sums up. I'll think what can be done here (parallelizing requests won't be an easy task).

Revision history for this message
Timur Sufiev (tsufiev-x) wrote :

Too hard to decrease time of loading first page in Horizon given current page architecture. The problem may be eliminated once it moves to AngularJS. Setting to Won't Fix.

Changed in mos:
status: Incomplete → Won't Fix
Revision history for this message
Satish Patel (satish-txt) wrote :

I know its very old post but i am seeing slowness too with 150 compute node.. 10 to 20 second for any action.. I am using queens.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.