Archived
This forum has been archived. Please start a new discussion on GitHub.
Java socket buffer size / gigabit network
Hi -
In debugging the time it takes to transfer large objects, we enabled network tracing and see this when running a Java ICE client against a local Java ICE server:
-- 8/23/10 19:21:47:141 Server: Network: received 65536 of 65536 bytes via tcp
local address = 127.0.0.1:25100
remote address = 127.0.0.1:54445
This repeats for dozens of messages.
We suspect this has something to do with the send and receive buffer sizes not being set on the socket connections. (see: Socket (Java Platform SE 6))
Is this possible?
Is there some workaround to override the values used?
We're on a gigabit network, so it makes sense that we'd have to size these values differently.
Thanks in advance!
(Environment: ICE 3.4.1 using JDK 1.6u21 tried on Windows 7 and CentOS 5)
In debugging the time it takes to transfer large objects, we enabled network tracing and see this when running a Java ICE client against a local Java ICE server:
-- 8/23/10 19:21:47:141 Server: Network: received 65536 of 65536 bytes via tcp
local address = 127.0.0.1:25100
remote address = 127.0.0.1:54445
This repeats for dozens of messages.
We suspect this has something to do with the send and receive buffer sizes not being set on the socket connections. (see: Socket (Java Platform SE 6))
Is this possible?
Is there some workaround to override the values used?
We're on a gigabit network, so it makes sense that we'd have to size these values differently.
Thanks in advance!
(Environment: ICE 3.4.1 using JDK 1.6u21 tried on Windows 7 and CentOS 5)
0
