Howdy,
Huh? Have you considered commons-pool?
(http://jakarta.apache.org/commons/pool/)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: David Boyer [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 27, 2003 3:02 PM
To: [EMAIL PROTECTED]
Subject: New Object Pooling
Hi all,
I've released a beta of my Object Pooling software and it's freely
available on my web site:
http://web.bvu.edu/staff/david/pooling/
This is an extensible Object Pooling system that could be extending to
handle pooling of just about any Object type. The initial release
contains
of object
pooling, like the reduction of memory defragmentation or the
reduction of memory usage.
I prefer to use pooled objects either for relative small number of
long lived objects or for objects that are expensive to create, or
immutable objects that consume some memory and are likely
On Tue, 2003-02-04 at 00:34, Ralph Einfeldt wrote:
I prefer to use pooled objects either for relative small number of
long lived objects or for objects that are expensive to create, or
immutable objects that consume some memory and are likely to be in
use concurrently.
Pooling is actually a
I prefer to use pooled objects either for relative small number of
long lived objects or for objects that are expensive to create, or
immutable objects that consume some memory and are likely to be in
use concurrently.
And what you think about objects that are created millions of times
and
From: Erik Price [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 2:16 PM
Subject: Re: more about custam tag life cycle
Are you saying that in general, object pooling is deprecated? In other
words, it's always a bad idea, with the exception of DataSource type
pools?
As a design issue
Will Hartung wrote:
From: Erik Price [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 2:16 PM
Subject: Re: more about custam tag life cycle
Are you saying that in general, object pooling is deprecated? In other
words, it's always a bad idea, with the exception of DataSource type
pools
complexity will give you.
Regards,
Will Hartung
([EMAIL PROTECTED])
- Original Message -
From: Felipe Schnack [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, December 23, 2002 1:10 PM
Subject: RE: Object Pooling
Yes... I guess I didn't know the difference
an module ID and who can access it (by
user id, user profession, etc). I was thinking about loading all of them
in memory at system startup and update them from time to time (or using
Observable interfaces)?
What do you think about it?
You may want to pursue object pooling, but the prevailing
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 2:52 PM
To: Tomcat Users List
Subject: Re: Object Pooling
I'm rewriting this reply, maybe I wasn't clear enough :-)
My application have two types of objects
, shouldn't I? Or maybe the effort doesn't pay?
On Mon, 2002-12-23 at 18:52, Tim Moore wrote:
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 2:52 PM
To: Tomcat Users List
Subject: Re: Object Pooling
I'm rewriting this reply
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 4:11 PM
To: Tomcat Users List
Subject: RE: Object Pooling
Yes... I guess I didn't know the difference between caching
and pooling.
Anyway, if now I got the idea, I should
On Mon, 2002-12-23 at 11:52, Felipe Schnack wrote:
My application have two types of objects that are constantly created
and destroyed. I believe that they could be pooled in some way (maybe
using commons pooling package. These types are:
1- Objects that handle user interaction. Basically
On Mon, 23 Dec 2002, Tim Moore wrote:
Date: Mon, 23 Dec 2002 17:07:49 -0500
From: Tim Moore [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: Object Pooling
-Original Message-
From: Felipe Schnack [mailto
IMHO. Maybe I
could simply load all of them in memory at system startup and update them from
time to time (or using Observable interfaces)?
Suggestions?
You may want to pursue object pooling, but the prevailing conventional
wisdom is that it's not really necessary. Object Pooling is important
Maybe I should be posting this on a commons maillist or something?
Well, the problem is that I have some objects that I'm instantiaing
tons of times in my application, and so, I would like to pool them.
There is somewhere a good dummies guide to commons-pool jar? The
javadocs aren't enough
On Fri, 2002-12-20 at 11:00, Felipe Schnack wrote:
Maybe I should be posting this on a commons maillist or something?
Well, the problem is that I have some objects that I'm instantiaing
tons of times in my application, and so, I would like to pool them.
There is somewhere a good dummies
You may want to pursue object pooling, but the prevailing conventional
wisdom is that it's not really necessary. Object Pooling is important for
objects that are particularly expensive to create (due to internal object
requirements, like connecting to external resources) and is not really
PROTECTED]
Subject: Re: Tag object pooling and immutability in the servlet spec
Craig R. McClanahan [EMAIL PROTECTED] wrote in message
news:20021025095901.K36250-10;icarus.apache.org...
On 24 Oct 2002, Mr. Tomcat wrote:
Date: 24 Oct 2002 17:37:36 -1000
From: Mr. Tomcat
]
Subject: Tag object pooling and immutability in the servlet spec
Is there a way to turn off tag object pooling? Object pooling was a
cool performance technique in earlier versions of Java, but now object
creation is very fast, so it no longer serves a performance function,
and it introduces
On Sat, 26 Oct 2002, Bill Barker wrote:
Date: Sat, 26 Oct 2002 23:57:55 -0700
From: Bill Barker [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Tag object pooling and immutability in the servlet spec
Craig R. McClanahan [EMAIL PROTECTED
Mr. Tomcat wrote:
Is there a way to turn off tag object pooling? Object pooling was a
cool performance technique in earlier versions of Java, but now object
creation is very fast, so it no longer serves a performance function,
and it introduces extra complexity into tag object design
On 24 Oct 2002, Mr. Tomcat wrote:
Date: 24 Oct 2002 17:37:36 -1000
From: Mr. Tomcat [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Tag object pooling and immutability in the servlet spec
Is there a way to turn off tag object pooling
Is there a way to turn off tag object pooling? Object pooling was a
cool performance technique in earlier versions of Java, but now object
creation is very fast, so it no longer serves a performance function,
and it introduces extra complexity into tag object design. Is this
misfeature going
You might post this on [EMAIL PROTECTED] instead
- Andrew
-Original Message-
From: John Walstra [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 05, 2002 1:23 AM
To: Tomcat Mailing List
Subject: Object pooling
Hi ya,
I'm trying to pool some objects. The objects consist
Hi ya,
I'm trying to pool some objects. The objects consist of a hash filled in from
XML files. I don't really want to reload the objects for each page hit and
it's used by an object that can't be scoped for the application. I've grabbed
commons-pool and incorporated it into my code. I have
26 matches
Mail list logo
