Bug #4349
closed
Switching tabs in the webapp is extremely slow
Added by Dennis Cabooter almost 11 years ago.
Updated almost 10 years ago.
Category:
Performance and scalability
Description
Switching tabs in the webapp is extremely slow. Sometimes it's fast, but mostly slow. I takes ~ 40 secs to switch from "Node management" to "Configuration policy", for example.
To make myself more clear; the slowness when switching tabs was already on 2.6 and 2.8.
- Target version set to 2.6.10
Thank you Dennis for reporting.
I don't know what could possibly do that:
Maybe some request are slow (reporting is checked for every Rule, so lots of requests, but it should be all fast or all slow, not some slow or some fast ...)
And you said to me on IRC that it was either when switching in and switching out Rule page ? or whatever page ?
Thanks for reporting.
We are trying to work on that, and to minimize things when switching. Some work was done in 2.7 and 2.8 to make things quicker. But 40s is just not bearable (so there is still A LOT to do ;)
In general, it's a given screen that is not fast, because some data are processed or badly used when it's loaded.
So, do you see that waiting when arriving on all tab ? Or only the configuration management one ? If so, does switching from Directive to Rules leads to the same time ? Does reloading Rules to ?
- Target version changed from 2.6.10 to 2.6.11
An update on that one: we found #4497 that may be responsible to the behaviour described here, and could match the observed behaviour.
- Target version changed from 2.6.11 to 2.6.12
- Target version changed from 2.6.12 to 2.6.13
- Target version changed from 2.6.13 to 2.6.14
- Target version changed from 2.6.14 to 2.6.16
- Target version changed from 2.6.16 to 2.6.17
- Target version changed from 2.6.17 to 2.6.18
- Target version changed from 2.6.18 to 2.6.19
- Target version changed from 2.6.19 to 2.6.20
- Category set to Performance and scalability
- Status changed from New to Rejected
- Target version changed from 2.6.20 to 2.10.10
I'm going to close that one. A LOT of work was done on that subject since that time, to the extends that in 3.0, displaying the list of 2000 nodes takes ~100ms.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by Nicolas PERRON 
Updated by Matthieu CERDA