Hello Victor,
thanks for your answer. This subject is really critical for my application,
at the moment. So my only chance is to implement it myself. At least, I'm
going to try. In case of succes, I'll post changes in this mailing list...
Tibor
- Original Message -
From: Victor Mote
Tibor Vyletel wrote:
thanks for your answer. This subject is really critical for my
application,
at the moment. So my only chance is to implement it myself. At least, I'm
going to try. In case of succes, I'll post changes in this mailing list...
It is pretty critical for what I am working
Mea (tool) culpa!
I am investigating an inaccuracy in CPU measurements reported
by the Java Memory Profiler Tool that led me to the conclusion
thet PropertyList.findProperty is the high-runner in FOP 0.20.5.
A couple of other profilers report that findProperty() uses more
CPU than we would like
John Austin wrote:
A high runner in FOP 0.20.5 is: PropertyList.findProperty().
It calls other functions in org.apache.fop.fo that consume
significant CPU resources. In one example it called itself
recursively to a (depth of 10)
Without taking a closer look at the code, I suspect it tries
to find
-Original Message-
From: Finn Bock [mailto:[EMAIL PROTECTED]
I can see performance slow down well before 100.000 unique string are
interned.
snip /
I've attached another demo program that shows that intern'ing is slower
than doing memory sharing with a Hashtable. This programs
-Original Message-
From: Andreas L. Delmelle [mailto:[EMAIL PROTECTED]
for(int i= cnt; --i = cnt; )
sorry. meant 0
cheers,
andreas