cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lars Huttar <>
Subject Re: Is ESQL/xsp supposed to stream?
Date Mon, 25 Jul 2005 18:00:37 GMT
Joel McConaughy wrote:

>Thanks for the quick reply.  I should have added some additional info:
>- This is in a noncaching pipeline with outputBufferSize=256000
>- From the mysql client, the query begins to return rows almost immediately.
>- Using the status link in the samples, I can see the JVM memory usage
>growing to the size of the total result set.
>- I can remove the stx transform and the xsp sill caches.
>Is there any way to get more visibility on what is going on inside the xsp
>Joel McConaughy
>Managing Partner
>Displayware LLC
>800 Fifth Ave., #101-316
>Seattle, WA 98104-3191
>206-300-4732 Direct
>206-382-2188 Fax
>-----Original Message-----
>From: Geert Josten [] 
>Sent: Monday, July 25, 2005 7:12 AM
>Subject: Re: Is ESQL/xsp supposed to stream?
>Hi Joel,
>Several cases are possible. Are you sure the xsp generator is caching, or
>does esql simply take a 
>lot of time to gather the table and starts looping over the records only
>once it has received them 
>all? Secondly, stx transformer could cache as well. Finally, there are
>options with which 
>serializers can be told to 'cache' results as well, to be able set a correct
>value for the 
>content-length field.
>I think you should start with adding logging instructions to your xsp page,
>to help clarify whether 
>the time delay occurs in the xsp (and where) or after the xsp step...
>Joel McConaughy wrote:
>>I'm trying to use the serverpages generator with ESQL and the stx 
>>transfomer to process large database tables.  The serverpages 
>>generator is not streaming but rather caches the entire contents of 
>>the query before passing data to the stx transformer.  Is this 
>>expected behavior?  Is there a way to configure this to stream the 
>>Thanks, Joel
>>cocoon 2.1.7, jdk1.4.2_08, mysql4.1.11, mysql_connectorj3.1.10
Is "cache" being used in two different (and orthogonal) senses here -- 
caching as opposed to streaming, and caching as opposed to recomputing 
when requested again?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message