[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [zzdev] Re: [Gzigzag-commits] gzigzag/src/util/test BenchPool.java
- To: "B. Fallenstein" <b.fallenstein@xxxxxx>
- Subject: Re: [zzdev] Re: [Gzigzag-commits] gzigzag/src/util/test BenchPool.java
- From: Tuomas Lukka <lukka@xxxxxxxxxx>
- Date: Mon, 3 Sep 2001 14:35:05 +0300
- Cc: ZZ Development <zzdev@xxxxxxxxxx>
- In-reply-to: <3B9337DC.17EC1CBE@xxxxxx>; from b.fallenstein@xxxxxx on Mon, Sep 03, 2001 at 09:57:16AM +0200
- Mail-followup-to: "B. Fallenstein" <b.fallenstein@xxxxxx>, ZZ Development <zzdev@xxxxxxxxxx>
- References: <E15dmej-0003zA-00@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <3B9337DC.17EC1CBE@xxxxxx>
> 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?
Needs two blockpools. That's all.
Tuomas