Performance Tuning SE-5.0
I am working on Informix SE 5.0 -AIX Platform. I have two tables one master and child. Both contains more than 2.5 lakh rows. Quering these tables takes hell of a day. I have used bcheck, update statistics also but in vain. As i would not be able to delete any of these rows because every row is required for future or present purpose. It is something like datawarehousing. Help me to solve the problem. How should i optimize the table to get good results. Regarding Hardware it is in BULL dpx20 RISC based. thanks in advance. Sent via Deja.com http://www.deja.com/
Not much I'm afraid. Make sure you have maxed out your OS buffers, and make sure you have the right indexes. In the year of Our Lord Sun, 17 Dec 2000 11:29:32 GMT, heyram@my-deja.com broke a vow of silence to utter: >I am working on Informix SE 5.0 -AIX Platform. I have two tables one >master and child. Both contains more than 2.5 lakh rows. Quering these >tables takes hell of a day. I have used bcheck, update statistics also >but in vain. As i would not be able to delete any of these rows because >every row is required for future or present purpose. It is something >like datawarehousing. Help me to solve the problem. How should i >optimize the table to get good results. Regarding Hardware it is in >BULL dpx20 RISC based. > >thanks in advance. > > >Sent via Deja.com >http://www.deja.com/
heyram@my-deja.com wrote: > I am working on Informix SE 5.0 -AIX Platform. I have two tables one > master and child. Both contains more than 2.5 lakh rows. A lakh being 100,000 rows. > Quering these tables takes hell of a day. What does SET EXPLAIN ON tell you about the queries? > I have used bcheck, update statistics also > but in vain. As i would not be able to delete any of these rows because > every row is required for future or present purpose. It is something > like datawarehousing. Help me to solve the problem. How should i > optimize the table to get good results. Regarding Hardware it is in > BULL dpx20 RISC based. You might improve performance if you store the two tables on separate disks, but that is a second order effect. To resolve the performance problem, find out what the optimizer is doing. If it is the best possible query plan (and there is no way to modify it to make it faster), then you can move on to the minor optimizations. If there is a missing index or something similar, then you can fix that instead. I'd also point out that 5.0x SE is not supported; it is not officially Y2K-compliant. You should upgrade to SE 5.10. -- Yours, Jonathan Leffler (Jonathan.Leffler@Informix.com) #include <disclaimer.h> Guardian of DBD::Informix v1.00.PC1 -- http://www.perl.com/CPAN "I don't suffer from insanity; I enjoy every minute of it!"