[JIRA] (JENKINS-38691) Sub-par write performance in JNLPv4 NIONetwork layer
Title: Message Title James Nord reopened an issue Jenkins / JENKINS-38691 Sub-par write performance in JNLPv4 NIONetwork layer Change By: James Nord Resolution: Fixed Status: Closed Reopened 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-38691) Sub-par write performance in JNLPv4 NIONetwork layer
Title: Message Title James Nord closed an issue as Won't Fix Jenkins / JENKINS-38691 Sub-par write performance in JNLPv4 NIONetwork layer Change By: James Nord Status: Reopened Closed Resolution: Won't Fix 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-38691) Sub-par write performance in JNLPv4 NIONetwork layer
Title: Message Title James Nord closed an issue as Fixed stephenconnolly] looked at this and tried an implementation - but it did not improve performance and used more heap Jenkins / JENKINS-38691 Sub-par write performance in JNLPv4 NIONetwork layer Change By: James Nord Status: Open 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 receiving emails from it, send an email to
[JIRA] (JENKINS-38691) Sub-par write performance in JNLPv4 NIONetwork layer
Title: Message Title James Nord edited a comment on JENKINS-38691 Re: Sub-par write performance in JNLPv4 NIONetwork layer [~stephenconnolly] ] looked at this and tried an implementation - but it did not improve performance and used more heap 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-38691) Sub-par write performance in JNLPv4 NIONetwork layer
Title: Message Title James Nord created an issue Jenkins / JENKINS-38691 Sub-par write performance in JNLPv4 NIONetwork layer Issue Type: Bug Assignee: James Nord Components: remoting Created: 2016/Oct/04 11:35 AM Priority: Major Reporter: James Nord The JNLP v2 protocol has a sub par write implementation if there is more than one buffers worth of data to be written to the network. The current implementation writes one buffers worth and then exits - waiting for another callback from the selector before writing another buffer. The code should write as much data as possible before returning back. see https://github.com/jenkinsci/remoting/blob/c3e675c9f1dc29a8fd99eca191c1ce1e5ebb2a7e/src/main/java/org/jenkinsci/remoting/protocol/impl/NIONetworkLayer.java#L191-L227 Add Comment
