Re: statistics
Posted in 2006
Topics: Performance & Tuning, Stored Procedures & SPL
On Fri, 7 Jul 2006 13:19:29 -0400, "Campbell, John \\(GE Cons Fin\\)" <John.Campbell2@ge.com> wrote: >Yes, I am very reluctant to mash on any system tables. This load routine runs a stored procedure every day that does an update/insert. If row found update it - if not insert it. After 3 or 4 days performance degrades significantly and deliverables are delayed. We didn't see this at first but the volume has been consistently increasing for two years. Running update statistics after the load process resolves the performance problem. It was suggested that I could keep the old statistics and put them back after the load process to avoid this problem and save time. I am skeptical and definitely wanted a second opinion. Responses so far have not been in favor of the idea... > How often does this load take place? is it a batch update / insert or a trickle-type job? Could you update stats on the table at a given time of day using cron? JWC
Its a batch update/insert. Recently, I've been running statistics on them every other evening. I have a script and do plan to put it in cron. Right now it doesn't take long to run stats - there's not that much volume. I don't know how long that will hold true... Thanks to you and everyone for your responses - they are very helpful. -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org]On Behalf Of John Carlson Sent: Wednesday, July 12, 2006 12:10 AM To: informix-list@iiug.org Subject: Re: statistics On Fri, 7 Jul 2006 13:19:29 -0400, "Campbell, John \\(GE Cons Fin\\)" <John.Campbell2@ge.com> wrote: >Yes, I am very reluctant to mash on any system tables. This load routine runs a stored procedure every day that does an update/insert. If row found update it - if not insert it. After 3 or 4 days performance degrades significantly and deliverables are delayed. We didn't see this at first but the volume has been consistently increasing for two years. Running update statistics after the load process resolves the performance problem. It was suggested that I could keep the old statistics and put them back after the load process to avoid this problem and save time. I am skeptical and definitely wanted a second opinion. Responses so far have not been in favor of the idea... > How often does this load take place? is it a batch update / insert or a trickle-type job? Could you update stats on the table at a given time of day using cron? JWC _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list