As reported in https://issues.jenkins.io/browse/JENKINS-49347?focusedCommentId=400609&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-400609 Blue Ocean starves browsers of sockets because each open Blue Ocean tab does {{GET}}s which intentionally take 30s to complete.

It doesn't take too many tabs open to Blue Ocean pages to have them all starving out the socket pool to that server with 30s {{GET}}s.

This makes Blue Ocean for all but very casual/lightweight users impossible to use.  It's certainly not usable by a full time developer that may have many job running on a given Jenkins instance and wants to monitor each of those jobs.

Additionally, opening and closing B/O views to work around this issue, when one has many jobs is also impractical just because of how long B/O pages take to load, even without many tabs competing to tie up sockets for 30s.