Hi,
for initial testing I often disable -server. In later tests I use it of
course too :)
The problem with the greater footprint is simple described: I've made
the first tests with 5.000-10.000 cocurrent connections. Under heavy
load the server permanently run out of space and started swapping. Ok,
1GB RAM isn't much for such a test, but on the other side these tests
didn't make useful things. When I implement more functionality at this
point, the same happens on 2 or 4GB RAM too I think.
Regards
Michael
[EMAIL PROTECTED] wrote:
Out of curiosity, why do you not use -server?
One serious issue with direct buffers is that you can declare a lot of
them, throw away the reference and the memory will not be reclaimed
until the GC kicks in. This may not be for some time since it depends
what is in the heap. Even if you allocate huge direct buffers it isn't
going to make GC happen any more quickly. I think it would have been
better if ByteBuffer had a dispose() method.
Since you find that heap buffers offer better performance for you, is
the greater memory footprint with direct buffers really an issue for you?
RG
