[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [Gzigzag-commits] gzigzag/src/util/test BenchPool.java
- To: ZZ Development <zzdev@xxxxxxxxxx>
- Subject: Re: [Gzigzag-commits] gzigzag/src/util/test BenchPool.java
- From: "B. Fallenstein" <b.fallenstein@xxxxxx>
- Date: Mon, 03 Sep 2001 09:57:16 +0200
- References: <E15dmej-0003zA-00@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
"Tuomas J. Lukka" wrote:
> Modified Files:
> BenchPool.java
> Log Message:
> A faster, simpler (but less functional) pool
Definitely sounds intriguing! But how does this work with the "strange"
lifecycles of Vob objects:
a) We create VobScene 1.
b) We create VobScene 2.
< we interpolate 1->2 >
c) We release VobScene 1.
d) We create VobScene 3.
< we interpolate 2->3 >
e) We release VobScene 2.
f) We create VobScene 4...
And it's views, after all, for which pooling is most useful (because
objects aren't kept for a long time). Or are there other important areas
of application?
-b.