[JIRA] (JENKINS-41212) Analyse and optimize SSE event traffic going to browser
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41212 Analyse and optimize SSE event traffic going to browser Change By: James Dumay Sprint: 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41212) Analyse and optimize SSE event traffic going to browser
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41212 Analyse and optimize SSE event traffic going to browser Change By: James Dumay Sprint: 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41212) Analyse and optimize SSE event traffic going to browser
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41212 Analyse and optimize SSE event traffic going to browser Change By: James Dumay Sprint: up next Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41212) Analyse and optimize SSE event traffic going to browser
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41212 Analyse and optimize SSE event traffic going to browser Change By: James Dumay Sprint: post-release up next 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-41212) Analyse and optimize SSE event traffic going to browser
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-41212
Analyse and optimize SSE event traffic going to browser
Change By:
Tom FENNELLY
I notice that when sitting on a Blue Ocean page for pipeline A, I'm also seeing SSE even traffic coming to the browser for pipelines B, C etc.Would be good to analyse how we're subscribing to these SSE events and maybe see if we can optimise things a bit. Obviously there are tradeoffs wrt complexity of the client-side code etc, but we should at least analyse it a bit.Tip: Trun Turn on client-side logging via the {{org.jenkinsci.sse}} log category.
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-41212) Analyse and optimize SSE event traffic going to browser
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-41212 Analyse and optimize SSE event traffic going to browser Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/19 11:34 AM Priority: Minor Reporter: Tom FENNELLY I notice that when sitting on a Blue Ocean page for pipeline A, I'm also seeing SSE even traffic coming to the browser for pipelines B, C etc. Would be good to analyse how we're subscribing to these SSE events and maybe see if we can optimise things a bit. Obviously there are tradeoffs wrt complexity of the client-side code etc, but we should at least analyse it a bit. Tip: Trun on client-side logging via the org.jenkinsci.sse log category. Add Comment
