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
| Michael Bauroth <[EMAIL PROTECTED]>
30/04/2006 17:51
|
To: [email protected] cc: Subject: Re: Performance - some interesting results |
Sun JDK 1.5.0_06 (no -server setting)
I'll try more cases next week. The main problem for me is the more
memory intensive direct buffer. Have you an idea, why this happens?
Regards
Michael
[EMAIL PROTECTED] wrote:
>
> Which JVM were you using?
>
> Robert
>
>
> *Michael Bauroth <[EMAIL PROTECTED]>*
>
> 29/04/2006 23:58
> Please respond to mina-dev
>
>
> To: [email protected]
> cc:
> Subject: Re: Performance - some interesting results
>
>
>
>
> Some more test results on a single Xeon machine (OS Debian 3.1 with
> Kernel 2.4.27)
>
> using 2 virtual machines (one as client, one as server).
>
> it happens only transmitting and consuming the data between the two.
>
> following happens:
>
> config: heap buffer against direct buffer
> memory consumption: 10% lesser with heap buffer use
> performance: 10% lesser with direct buffer use
>
> Will make the same tests once more with Kernel 2.6 next week.
>
> Regards
> Michael
>
>
>
> This communication is for informational purposes only. It is not intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All market
> prices,
> data and other information are not warranted as to completeness or
> accuracy and
> are subject to change without notice. Any comments or statements made
> herein
> do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
> and affiliates.
This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
