Re: write cache / NETTYPE

>From: "Obnoxio The Clown" <obnoxio@hotmail.com> >To: Valerie.H.Webber@m1.irs.gov, informix-list@iiug.org >Subject: Re: write cache / NETTYPE >Date: Fri, 24 Sep 1999 13:46:43 BST > >From: Webber Valerie H <Valerie.H.Webber@m1.irs.gov> >> >>How important is the % Write cache on the onstat -p (listed below)? I read >>you should shoot for 85%..... ours is very low... 8% and sometimes 0%. How >>do you tune the database for write cache. We do mostly reads and inserts >>and >>very few updates. > >If your users aren't complaining, you don't have a problem. :-) Agreed. If the users are happy it is not broken. It is not always possible to get a high write cache rate. What are your percentage of reads compared to writes? Look at onstat -g iof and compare dskread to dskwrite. If you are doing mostly reads then that makes the write cache even less significant. > >Because you have LRU_MIN_DIRTY and LRU_MAX_DIRTY set so low, your buffers >are being flushed before they can, uh, buffer anything. If your system's >performance is acceptable, I guess this is OK. > >You can amend the figures you're seeing by increasing BUFFERS or increasing >LRU_MIN_DIRTY and LRU_MAX_DIRTY. > >>Also does anyone have some information about NETTYPE. We only have one >>NETTYPE (VP class: CPU) in our onconfig. I see other people with 2 (CPU >>and >>NET.) How do you determine what you need? > >You use a NET NETTYPE for client/server (TCP/IP) connections. If you're not >using TCP/IP, then you don't need NET NETTYPEs. (I think it will >automagically configure one by default anyway, can't remember the >parameters >off-hand.) > > >______________________________________________________ >Get Your Private, Free Email at http://www.hotmail.com ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com