Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 10372 invoked from network); 25 Jul 2005 17:59:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2005 17:59:13 -0000 Received: (qmail 10202 invoked by uid 500); 25 Jul 2005 17:59:03 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 10160 invoked by uid 500); 25 Jul 2005 17:59:03 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 10147 invoked by uid 99); 25 Jul 2005 17:59:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2005 10:59:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lars_huttar@sil.org designates 208.145.81.85 as permitted sender) Received: from [208.145.81.85] (HELO mail.link77.net) (208.145.81.85) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2005 10:58:56 -0700 X-Scanned-By: RAE MPP/Clamd http://raeinternet.com/mpp Received: from [172.20.5.114] (account lars_huttar@sil.org [172.20.5.114] verified) by mail.link77.net (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 79581829 for users@cocoon.apache.org; Mon, 25 Jul 2005 13:58:59 -0400 Message-ID: <42E528C5.4000701@sil.org> Date: Mon, 25 Jul 2005 13:00:37 -0500 From: Lars Huttar Organization: SIL User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: Is ESQL/xsp supposed to stream? References: <004201c59124$f8145760$1eb6fea9@JOEL> In-Reply-To: <004201c59124$f8145760$1eb6fea9@JOEL> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Joel McConaughy wrote: >Geert, > >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 >generator? > >Joel > > >Joel McConaughy >Managing Partner >Displayware LLC >800 Fifth Ave., #101-316 >Seattle, WA 98104-3191 >206-300-4732 Direct >206-382-2188 Fax >joel@displayware.com > > >-----Original Message----- >From: Geert Josten [mailto:Geert.Josten@daidalos.nl] >Sent: Monday, July 25, 2005 7:12 AM >To: users@cocoon.apache.org >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... > >HTH, >Geert > >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 >>results? >> >>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? Lars --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org