Hi! Everybody try to fight against this. :-D
Please note that ESQL is fast enough. It can build the 8,000 rowset in milisecs. Problem starts when the rowset go trought some XSL transformations and serialization. The worse if that after you render this to HTML. The client browser can spend more than this 3.5 to render all of this. I made some test and for 10,000 rows. It can take more than 5 mins on a Pentium IV 2.0 GHz with 256 MB of RAM to render it after Cocoon sent back the HTML page! In a slower computer with less memory it can takes more than 15 mins! Please note that this is not a ESQL issue. This is just related to ESQL. I think if you can build a page with 8,000 rows without using ESQL you will get the same result. To workaround this issue you must "paginate" the responses instead of responde with a big bulk of data. I think people will not read all the 8,000 or more rows. :-D To paginate the answers, use the tags: <esql:skip-rows> and <esql:max-rows>. Best Regards, Antonio Gallardo.
