socket high perfomance

SERVER * Console execution parameters: I think we can eliminate writing the command in console example I on the server I run it in the console in the way java -cp [login to view URL] [login to view URL] [login to view URL] 9797 8080, I think it is unnecessary, it is better to leave the IP in this case I always use [login to view URL] it is standard always configTargetPort port in static code and leave it as 9797 and configPort port we will make a multiport that is, it will no longer only run 8080. You can leave this value in code as 8080, 9090, 3128. (with this that is to say stop writing the parameters in consoles and leave it static in the code much better with this it would be left to run it as follows) java -cp [login to view URL] [login to view URL] * Executor Service: I add the executor to improve the performance of the client's packages, be faster and create queues of ready requests ready only to be used, in this way it improves the performance, but the detail is that I don't think I add it in the correct way. It would be to do it correctly, you can read the example of supertunnel it has it but remember that the supertunnel sends the request in another way for this reason. You would only take an example of how he executes it and perhaps as you see fit. * SoftReference: This according to what I read is very useful for the socket since it helps to clean the memory, which I don't know if this can be added to the CLIENT as well, there is a repo that server socket that uses it, I just leave it as an example so that see what way he uses it. [login to view URL] * Compressor and decompressor The server sends a request to the client sends a size, but of course if you read the client it sends the server what quantity or what exact size it will send and returns it to the client the amount that the client sent doReceiveRequest exactly where it receives the value is writeServerSize this value It has to be compressed so that when it passes through the network or firewall, its size is smaller and it reaches the client, it is decompressed and its traffic generates its real value. This helps us to save bandwidth and improve the speed on the network, is what I think. using (SHAPPY JAVA or COMP-LZO) shappy is much faster and compresses a lot according to the examples, then with this the server and client the information that sends and receives both will compress and decompress to have at the end its real value. (writeServerSize - writeServerReceiveSize). ANY OTHER IDEA OF YOURS THAT YOU THINK MAY IMPROVE PERFOMANCE ACCORDING TO YOUR KNOWLEDGE. TESTBYTES ARRAYS: * SEND AND RECEIVE I explain the goal and it works from this so you understand my goal a bit: You know very well that my project is to bypass the firewall, that due to a small TCP traffic it keeps the connection stable due to the multiple responses it makes. So what makes this special is to measure the number of bytes that can pass through the firewall, it calculates but how it measures the amount of what it receives and what I want to do is measure the amount received and sent and the client obtains the values ​​both values ​​how much was his maximum when receiving and sending. Because if you notice he gives you the information of the best POST example request [login to view URL] HTTP / 1.1 / r / n and then writes the client that we have jorstunnel to do the bypass to the firewall according to how many bytes it can pass. I NEED TO HAVE VALUE ON THE CUSTOMER RECEIVE AND SEND PRINTED ON THE CUSTOMER * SERVER IS LOST OR STARTS The server crashes when it receives a lot of request or throws an error that it cannot lift the port and it stays down for a long time and I think it then gets up on its own, I just need help with this. send some parameter as the jorstunnel send # logic # for socket security or some password so that there are requests in another way without having the parameter