cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <h...@dvs1.informatik.tu-darmstadt.de>
Subject Re: strange database problem
Date Tue, 02 Jul 2002 15:21:15 GMT
On 02.Jul.2002 -- 04:05 PM, Leszek Gawron wrote:
> > It is the very same jadozoom driver. I cannot tell if the performance
> > degenerates but I think not. The difference is significant though.
> > 	ouzo
> here are some timings taken from cocoon log:
> 
> version somewhere round 2002.04.20
> INFO  HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev
in 270 milliseconds.
> 
> version 2002.07.01
> INFO  HttpProcessor[80][4]/CocoonServlet: 'xspxml/cdn' Processed by Apache Cocoon 2.1-dev
in 460 milliseconds.

That looks bad, indeed. I will have a look at it but it will take some
time to reproduce these values (gimme a week or so). I take your word
for it that you haven't changed anything else around it like move the
DBMS to another machine, upgrade your network, CPU, RAM, JDK, JDBC
driver or anything else.

However, I will not be able to test against your setup and use a
different DBMS / OS / JDK / Servlet-Container.

It would help to have some more information on the table, like number
and type of columns, number of rows.

If you care to do some experiments yourself, the ESQL stuff is fairly
self-contained and does not depend on other changes in Cocoon. Thus
it's only o.a.c.c.l.m.xsp/Esql*.java and o.a.c.c.l.m.xsp.java/esql.xsl

The resulting java code produced from your XSP should be fairly
similar with both versions, actually. 

The main difference should be the introduction of various switch
statements to select different results. Those are outside the
retrieval loop and so should not account for a big slow-down.

The other major difference should be, that the current version does
not check for another result set while the older version did (in a not
JDBC compliant way - that was changed to be compliant and later
disabled).

Other things happend in the grouping / CallableStatement support which
should not be used in your case.

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message