You have two issues, the caching in Postgres which is memory based and ofbiz caching of the recordset that is returned. I suggest you look at the number of instances of Postgres for the instance of ofbiz and the total memory available on the bos you are running on. also look at the indexing of the data you are searching on.
Foo Shyn Chung sent the following on 10/24/2011 3:39 AM: > I'm using Postgres as the database, i think it should support cursor fine. > Anyway the reason i'm asking this is that the client is facing load time > issue when they try to search out large amount of data. Although the result > is segregated by paging, it seems like it is still affecting the memory > usage. Hence i'm trying to figure out what's the problem. > > A lot of thanks for any comments or advice. > > Thank you > FooShyn > > On Wed, Oct 12, 2011 at 12:18 AM, BJ Freeman <[email protected]> wrote: > >> are you using an entity OTTB? >> Some DB will not handle Cursors. >> >> Foo Shyn Chung sent the following on 10/6/2011 12:48 AM: >>> Hi guys, >>> >>> Would like to ask what is the mechanism used in Ofbiz for multi page >>> listing? >>> >>> Currently we have a live site whereby the listing would resulted in a few >>> thousands rows being returned and displayed on multiple page on the >> screen. >>> We found that once the data amount hit a certain amount, the performance >> of >>> that page will become very slow. >>> >>> For listing, is Ofbiz will load up all the results in the memory, then >> only >>> segregate them into multiple page? or they only will load the data when >> the >>> user is viewing the page (i.e. when the user click next page, then the >> data >>> for the next page is loaded). >>> >>> Not sure whether anyone has encountered this before? >>> >>> Thank you >>> FooShyn >>> >> >
