-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
1.554.1 with
JENKINS-22822
We've got 1026 users on builds.apache.org, and when you try to view a user or go through a user's views, etc, load time is abominable most of the time - ~54 seconds or so in the example below. While we're seeing a lot of what might be i/o related slowness in other areas, this seems kind of insane. Does User.getAll() really need to reload every user's config.xml every 10 seconds?
- duplicates
-
JENKINS-47429 Absolutely atrocious user lookup performance when many legacy users
-
- Resolved
-
- is related to
-
JENKINS-47718 Deprecate User.getUser(String)
-
- Resolved
-
[JENKINS-23281] Jenkins.getUser(...) is debilitatingly slow with a large number of users
Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
Workflow | Original: JNJira [ 155846 ] | New: JNJira + In-Review [ 179140 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |