Hi Leo.

what are you trying to gain from this?

Here the criticism from the link you provided:

Criticism

Some publications do not recommend using object pooling with certain
languages, such as Java, especially for objects that only use memory and
hold no external
resources.[2]<http://en.wikipedia.org/wiki/Object_pool_pattern#cite_note-2>Opponents
usually say that object allocation is relatively fast in modern
languages with garbage
collectors<http://en.wikipedia.org/wiki/Garbage_collection_%28computer_science%29>;
while the operator new needs only ten instructions, the classic new -
deletepair found in pooling designs requires hundreds of them as it
does more
complex work. Also, most garbage collectors scan "live" object references,
and not the memory that these objects use for their content. This means
that any number of "dead" objects without references can be discarded with
little cost. In contrast, keeping a large number of "live" but unused
objects increases the duration of garbage
collection.[1]<http://en.wikipedia.org/wiki/Object_pool_pattern#cite_note-urban-1>In
some cases, programs that use garbage collection instead of directly
managing memory may run faster.


what do you say about this?

best regards,

Martin

On Mon, Dec 17, 2012 at 5:23 PM, Leonardo Uribe <lu4...@gmail.com> wrote:

> recover




-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Reply via email to