On Wed, 18 Jul 2001 13:43:07 Jeremias Maerki wrote:
> This sounds quite like the experiences by Jim Cotugno (See subject
> "Multithreading"). Some time ago I did some concurrency tests and it was
> interesting to see what happened. When multiple conversions occur
> concurrently FOP seems to align the processing like this:
> Let's say FOP does steps 1, 2 and 3 and we have conversions A, B, C and
> D which run more or less at the same time. The following seems to
> happen:
> A1, B1, C1, D1, A2, B2, C2, D2, A3, B3, C3, D3
> I happened to see that when I sent the output of every thread into the
> same console. It might very vell be, that this has something to do with
> the use of static variables. This also explains your experienced maximum
> of over 2 minutes.

I don't see how it could be static variables. I think the more likely cause
is from Vector and Hashtable. In other words we should go to jdk1.2 and get
rid of these bad classes (thats enough of my jdk1.1 bashing for the day).

> The topic "Avalon" has come up a few times over the last months. It has
> never got much attention. But it might help us to get rid of some of the
> performance problems just by reworking parts of FOP for Avalon. This
> could also result in a stable high-level interface for FOP which would
> probably cheer up a few people as well (Cocooners, Servlet-integrators
> etc.). What do you think?

Integrating Avalon should be done as soon as possible.

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to