parsl/executors/high_throughput/zmq_pipes.py
def run(self, message):
        """ This function needs to be fast at the same time aware of the possibility of
        ZMQ pipes overflowing.

        The timeout increases slowly if contention is detected on ZMQ pipes.
        We could set copy=False and get slightly better latency but this results
        in ZMQ sockets reaching a broken state once there are ~10k tasks in flight.
        This issue can be magnified if each the serialized buffer itself is larger.
        """
        self.zmq_socket.send_pyobj(message, copy=True)
        reply = self.zmq_socket.recv_pyobj()
        return reply
def run(self, message):
        """ This function needs to be fast at the same time aware of the possibility of
        ZMQ pipes overflowing.

        The timeout increases slowly if contention is detected on ZMQ pipes.
        We could set copy=False and get slightly better latency but this results
        in ZMQ sockets reaching a broken state once there are ~10k tasks in flight.
        This issue can be magnified if each the serialized buffer itself is larger.
        """
        self.zmq_socket.send_pyobj(message, copy=True)
        reply = self.zmq_socket.recv_pyobj()
        return reply
def run ( self , message ) : self . zmq_socket . send_pyobj ( message , copy = True ) reply = self . zmq_socket . recv_pyobj ( ) return reply
This function needs to be fast at the same time aware of the possibility of
        ZMQ pipes overflowing.

        The timeout increases slowly if contention is detected on ZMQ pipes.
        We could set copy=False and get slightly better latency but this results
        in ZMQ sockets reaching a broken state once there are ~10k tasks in flight.
        This issue can be magnified if each the serialized buffer itself is larger.
This function needs to be fast at the same time aware of the possibility of ZMQ pipes overflowing .