Thanks Mike -- don't think this is a cache issue -- at least not OFBiz cache since it is not showing up in the OFBiz Cache maintenance page. Nick
-----Original Message----- From: Mike [mailto:[email protected]] Sent: Tuesday, November 24, 2015 11:31 AM To: user <[email protected]> Subject: Re: VISIT and VISITOR Entities Most likely this table is stealing cache memory from the rest of the tables. Either increase cache memory, delete the rows, write to a separate database, or keep the table trim to xxx rows (as Adrian said) via an internal ofbiz job or external script (via crontab). On Tue, Nov 24, 2015 at 7:48 AM, Len Shein <[email protected]> wrote: > All, > > We have a LIVE application in which the VISIT AND VISITOR entities > have grown to over 19 and 18 million rows respectively. > > Has anyone experienced any performance issues when these entities have > grown to such capacity? > > > > We recently had a performance issue and decided to turn off the visit > history feature until this feature can be ruled out as the issue. > > stats.persist.visit=false > > stats.persist.visitor=false > > > > Note: The application is currently using Ofbiz r.10. > > > Len Shein > > <mailto:[email protected]> [email protected] > > O: 516.742.7888 x225 > > O: 732.333.4303 > C: 917.882.8515 > >
