[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale commented on JENKINS-38079 Re: Investigate performance degradation report see also: https://issues.jenkins-ci.org/browse/JENKINS-38335 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey closed an issue as Fixed Closing this issue. We have identified issues and opened tickets for relevant performance improvements in specific components: JENKINS-38251, JENKINS-38252, JENKINS-38253 and JENKINS-38087. Jenkins / JENKINS-38079 Investigate performance degradation report Change By: Vivek Pandey Status: In Progress Closed Resolution: Fixed 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
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title James Dumay commented on JENKINS-38079 Re: Investigate performance degradation report Thanks for filing this Andreas - fixing the performance issues above is a top priority for our team 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report Search API performance issue 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report Relates to search API performance issue. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title James Dumay commented on JENKINS-38079 Re: Investigate performance degradation report Tom FENNELLY you can upload the HAR to https://toolbox.googleapps.com/apps/har_analyzer/ and view the captured data and requests that occurred within the browser session. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Tom FENNELLY commented on JENKINS-38079 Re: Investigate performance degradation report A har file is a file you can generate from the network log panel in the dev tools in the browser. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale commented on JENKINS-38079 Re: Investigate performance degradation report Tom FENNELLY this starvation of things may be what has been seen elsewhere (with github oauth in some cases?). Also - can I ask a dumb question - what is a "HAR" ? 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Tom FENNELLY commented on JENKINS-38079 Re: Investigate performance degradation report Yeah, this is strange for sure from an SSE configure pov because the cost of what it is doing should be constant and small i.e. it is not searching anything or moving data around. I will look into this too from an SSE pov, but one thing I plan for this is to make the configure process completely async + remove all locking on the request path. Of course that will only have a limited effect if it's a case that the host is starved of threads from the request thread pool because of other long-running requests. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report Thanks Darragh Sherwin. This looks like search API performance issue as noted above, I will dig in to HAR file and get back. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Darragh Sherwin commented on JENKINS-38079 Re: Investigate performance degradation report As discussed at Jenkins World, HAR attached. Slownews when clicking on "Show More" 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Darragh Sherwin updated an issue Jenkins / JENKINS-38079 Investigate performance degradation report Change By: Darragh Sherwin Attachment: blue-ocean-slow.har 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale edited a comment on JENKINS-38079 Re: Investigate performance degradation report [~vivek] might be worth syncing up with [~tfennelly] so he is aware of these . (perhaps the SSE and js loading could be split off to him?) 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38079 Investigate performance degradation report Change By: Michael Neale Priority: Critical Blocker 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale commented on JENKINS-38079 Re: Investigate performance degradation report Vivek Pandey might be worth syncing up with Tom FENNELLY so he is aware of these. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey started work on JENKINS-38079 Change By: Vivek Pandey Status: Open In Progress 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey stopped work on JENKINS-38079 Change By: Vivek Pandey Status: In Progress Open 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report James Dumay it touches several aspects of BO. See key findings above. For example UI should stop sending redundant calls costing multiple of seconds, cache JS scripts across pages, investigate why SSE configure for job subscription is expensive, Favourite and search API performance etc. you should split it in to multiple tickets and assign right people to it. For favorite Ivan or me should look in to. I plan to take on search for sure. 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title James Dumay commented on JENKINS-38079 Re: Investigate performance degradation report Thanks Vivek Pandey - where are you going to start? 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey commented on JENKINS-38079 Re: Investigate performance degradation report I am summarizing here the findings, there are problems in different areas: favorites API is taking longer than usual and then SSE /configure API takes really long time. search API also takes long time, we can improve it but I am not too sure given how we want flattened/sorted list. Key Findings (actionable/'to be investigated' items) SSE SSE configure call takes really long time (~10sec) for job channel subscription (there are two job subscriptions) "subscribe": [ { "jenkins_channel": "job" } , { "jenkins_channel": "job" } ], SSE configure for pipeline channel is relatively less but still long time (3-4 sec) Avoid redirection by appending ‘/‘. GET /js-extensions costs 61ms Run details page calls SSE configure API 5 times each taking on average ~2secs. Favorites API (page limit 26) GET takes unreasonably long time 5.56 sec and there is only one favorited item!!! Favorite item is a pipeline object that includes latest Run. It also includes actions (changeset, branch details) so interacting with git (file IO, hope it doesn’t go all the way to github for that)? Needs investigation Search API (page limit 26) Took 7 sec on average To address sorting by name and exclude certain items from flattening all possible items are loaded in memory jenkins.getAllItems() Exclude items that are children of multi-branch and matrix project Don’t see how we can avoid it unless the jobs are stored in some kind of db with indexed column to speed up sorting and only give limited records instead of all new PipelineContainerImpl().getPipelines(items) should be pagination aware At present it creates BluePipeline object for all possible items (ouch!) Static Resources blueocean.js (642KB), 370 ms to load: is loaded on each page (dashboard, run details, pipeline) An so are most other JS files If these are cached (not fetched for each page can easily save few secs)
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Vivek Pandey started work on JENKINS-38079 Change By: Vivek Pandey Status: Open In Progress 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38079 Investigate performance degradation report Change By: James Dumay Sprint: 1.0-beta-1 , 1.0-b05/b-06 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.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title James Dumay created an issue Jenkins / JENKINS-38079 Investigate performance degradation report Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Sep/08 10:39 PM Priority: Critical Reporter: James Dumay See https://groups.google.com/forum/#!topic/jenkinsci-dev/wcoXynHvSIE Andreas has sent us HAR files and thread dumps out-of-band to investigate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)