Thanks Adrian -- we'll take a look at the latest version. Maybe a complete red herring -- but a couple of weeks ago our client requested that we change the password for the primary "admin" user. We deleted and re-added main scheduled jobs but we've had problems since ...
Nick -----Original Message----- From: Adrian Crum [mailto:adrian.c...@sandglass-software.com] Sent: Tuesday, November 24, 2015 11:58 AM To: user@ofbiz.apache.org Subject: Re: VISIT and VISITOR Entities Hmmm... it could be the job scheduler. It was refactored a few years ago to fix problems like that. Try C&Ping R13 job scheduler into R10 (framework\service\src\org\ofbiz\service\job). Adrian Crum Sandglass Software www.sandglass-software.com On 11/24/2015 8:29 AM, Nick Rosser wrote: > Adrian, > > Not entirely sure if it made a difference -- site was going down every now > and again, initially we thought that some scheduled jobs were the culprit > (since outages were in or around the scheduled job time). However, we had > problems yesterday when no scheduled jobs were running (we disabled most of > them for now). > > Site has been fine since we turned off VISIT and VISITOR tracking -- can't be > 100% sure that this is the resolution factor given general problems over the > last couple of weeks. I guess that if the site is fine for several days then > we would have to attribute it to the serverstats change. > > We've heard of problems when the JOB_SANDBOX gets very large -- ever heard > about instability when VISIT and VISITORS get very large? (19M and 18M rows > each). > > Nick > > -----Original Message----- > From: Adrian Crum [mailto:adrian.c...@sandglass-software.com] > Sent: Tuesday, November 24, 2015 11:13 AM > To: user@ofbiz.apache.org > Subject: Re: VISIT and VISITOR Entities > > Did the setting change improve performance? > > You could write a service that deletes data older than xxx days, then make it > a scheduled job. > > Adrian Crum > Sandglass Software > www.sandglass-software.com > > On 11/24/2015 7:48 AM, Len Shein 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:lsh...@solveda.com> lsh...@solveda.com >> >> O: 516.742.7888 x225 >> >> O: 732.333.4303 >> C: 917.882.8515 >> >>
