[JIRA] (JENKINS-37208) Slowness by too many calls in /wfapi/runs on complex pipelines

[svano...@cloudbees.com (JIRA)]

Title: Message Title

Sam Van Oort commented on JENKINS-37208   Re: Slowness by too many calls in /wfapi/runs on complex pipelines Félix Belzunce Arcos Stage view only returns or touches up to MAX_RUNS_PER_JOB (controlled by com.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob) runs for each job (default is 10). After the initial data fetch, it uses the "since" parameter to only return or examine net-new builds, further reducing request size. For each individual run, stage view hits a run data cache, keyed by project name and build number. If you open 40-50 tabs at once before the first request has completed, then there's not enough time for the data to be generated and hit cache... but that doesn't reflect the real-world use case. Generally you do not see many concurrent requests, but rather scattered requests over time (where the caching here can deliver up to 1000x the performance with large flow graphs). Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.