|Anonymous | Login | Signup for a new account||2019-09-19 01:02 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008761||TestLink||Req Overview||public||2019-09-11 13:13||2019-09-11 14:47|
|Product Version||1.9.19.01 (1.9.19 fixes)|
|Fixed in Version|
|Summary||0008761: Latencies when loading the page "Requirement Overview"|
|Description||In some use cases, processing time goes to more than one minute. There are two different reasons why we can notice latencies when loading the page “Requirement Overview”:|
Back-end reason (server side):
This latency happens when Custom Fields are present in a requirement. After having analyzed the implementation of this functionality, I found that two additional SQL queries are made for each requirement when requirements have Custom Fields related. The first one requests the project ID (that is useless) and the second one requests the Custom Fields value of the requirement (that can be optimized). I already have a good idea of how reduce this processing time, we could discuss it.
Front-end reason (client side):
Firefox seems not efficient with the use of Ext-JS (old version) and with more than about 2000 requirements. I have no real solution for this use case except upgrade or remove Ext-JS.
|Steps To Reproduce||- Having 1000 to 5000 requirements|
- Add custom fields related to requirement
- Try load the page "Requirement Overview"
|Additional Information||I made tests with 5000 requirements without any relation or other information. For each requirement, I added progressively relations with test cases (3/req) then relations with requirements (3/req) and finally custom fields (3/req).|
|Tags||No tags attached.|
|Browser||Firefox 68 / Chrome 75|
|PHP Version||PHP 7.2|
|QA Team - Task Workflow Status|
|Attached Files|| chrome.PNG [^] (21,240 bytes) 2019-09-11 13:13
firefox.PNG [^] (23,861 bytes) 2019-09-11 13:13
It would be great if the right pointer to the code is provided, in order to make things simpler.
When you said that something can be optimized is also important to have your findings, to avoid doing the same work twice.
The simple structure used to manage the tree on DB is know to create issues due to two the recursive nature.
|2019-09-11 13:13||c2pil||New Issue|
|2019-09-11 13:13||c2pil||File Added: chrome.PNG|
|2019-09-11 13:13||c2pil||File Added: firefox.PNG|
|2019-09-11 14:47||fman||Note Added: 0029151|
|Copyright © 2000 - 2019 MantisBT Team|