Content
View differences
Updated by Markus Kahl 20 days ago
Let us collect here all endpoints with persistent reports of bad performance, and collect any relevant information for each of the cases.
* /api/v3/work\_packages/:id/available\_relation\_candidates
* some of the problems were caused by this query being sent off too often, immediately with each press of a letter - this was improved in <mention class="mention" data-id="60649" data-type="work_package" data-text="##60649">##60649</mention> - but that didn't address the root cause which is the slow query
* \--------------------------------------------------
* the following are related to a large page size, this has been known, and is still something we definitely should optimize if possible (see <mention class="mention" data-id="68390" data-type="work_package" data-text="##68390">##68390</mention>) for an example
* \--------------------------------------------------
* /api/v3/time\_entries
* /api/v3/work\_packages
* /api/v3/projects
* /api/v3/work\_packages/:id/available\_relation\_candidates
* some of the problems were caused by this query being sent off too often, immediately with each press of a letter - this was improved in <mention class="mention" data-id="60649" data-type="work_package" data-text="##60649">##60649</mention> - but that didn't address the root cause which is the slow query
* \--------------------------------------------------
* the following are related to a large page size, this has been known, and is still something we definitely should optimize if possible (see <mention class="mention" data-id="68390" data-type="work_package" data-text="##68390">##68390</mention>) for an example
* \--------------------------------------------------
* /api/v3/time\_entries
* /api/v3/work\_packages
* /api/v3/projects