[FOLIO-1904] SPIKE: investigate which APIs contribute to MODUSERS-107 Created: 25/Mar/19  Updated: 03/Jun/20  Resolved: 02/Apr/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: Eric Valuk
Resolution: Cannot Reproduce Votes: 0
Labels: platform-backlog, q1-performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File bugfest.folio.ebsco.com.har     File user-details.bugfest.folio.ebsco.com.har     File user-details2.bugfest.folio.ebsco.com.har    
Issue links:
Blocks
blocks MODUSERS-107 Users App Slow to Display Users Closed
Cloners
clones FOLIO-1903 SPIKE: investigate which APIs contrib... Closed
Relates
relates to FOLIO-1894 add jMeter API test for searching sel... Closed
relates to MODUSERS-107 Users App Slow to Display Users Closed
Sprint: Core: Platform - Sprint 60
Story Points: 1
Development Team: Core: Platform

 Description   

Investigate (e.g using the Chrome devtools console) which APIs and searches contribute to the slow performance of searching users by username.



 Comments   
Comment by Eric Valuk [ 28/Mar/19 ]

Ive gone through several of the top time usage queries for these lists. They have extremely large % of time listed in trace for mod-authtoken approximately 7 seconds out of a 7.7 second query.

Proxiesfor and service-points both show this behavior. This is compounded by the fact that individually these requests dont have large response times. I have added them to the performance nightly job and tested them myself against the same environment as this bug and they perform reasonably fast. < 1 second average. A few might creep up over 1 second average.

I dont have an answer yet for why auth takes so long yet. Still looking into it.

Comment by Eric Valuk [ 02/Apr/19 ]

I ran a UI bundle against a performance build of FOLIO with more recent module deployments. I was not able to reproduce this issue.

Generated at Thu Feb 08 23:16:45 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.