-
Task
-
Resolution: Unresolved
-
Minor
-
None
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: Turn on client-side logging via the org.jenkinsci.sse log category.
[JENKINS-41212] Analyse and optimize SSE event traffic going to browser
Epic Link | New: JENKINS-37957 [ 174099 ] |
Description |
Original:
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. |
New:
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: Turn on client-side logging via the {{org.jenkinsci.sse}} log category. |
Sprint | Original: post-release [ 181 ] | New: up next [ 171 ] |
Rank | New: Ranked lower |
Sprint | Original: up next [ 171 ] |
Sprint | New: 1.1 [ 251 ] |
Rank | New: Ranked higher |
Sprint | Original: 1.1 [ 251 ] |
Rank | New: Ranked lower |