best praactices for chuck layout
OS: Suse 11SP4 IDS: 12.10FC6 Our ERP provider is forcing us to move from HPUX to Suse Linux and of course they need to do the migration so they can 'certify' the migration. So we have no real control of the setup of Informix. And moving to another ERP can't be done in the time before current ERP drops HPUX support. And we are required to have a supported ERP. We have a small amount of data about 30-35GB on the production DB compared to some Informix installs. And maybe I'm too old but I'm not liking the setup they made. So thought I would ask what is the best practice now for chunk layout. They created one big cooked file for dbs0 (production) and the same for dbs1 (test). On the HPUX I basically used 2GB chunks and made sure I had 1 year of free space or more. We have twice a year Federal Loan processes that can generate lots of records that have a short life so sometimes need a good buffer. So had 24 2GB chucks. Maybe not the greatest layout but never had problems with it since 1999 when we first setup Informix. To me this one big supper-sized chunk just seems a bad idea. Any words of wisdoms would be greatly appreciated. John Adamski Sr. Network Specialist Graceland University
The more active chunks you have the more parallelism the engine can use to read and flush IO. With a single huge chunk Informix can only use a single KAIO thread or AIO VP to perform reads and/or writes. That's the main effect. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Mar 23, 2017 at 10:14 PM, John Adamski (Work Account) < adamski@graceland.edu> wrote: > OS: Suse 11SP4 > > IDS: 12.10FC6 > > Our ERP provider is forcing us to move from HPUX to Suse Linux and of > course > they need to do the migration so they can 'certify' the migration. So we > have > no real control of the setup of Informix. And moving to another ERP can't > be > done in the time before current ERP drops HPUX support. And we are > required to > have a supported ERP. > > We have a small amount of data about 30-35GB on the production DB compared > to > some Informix installs. And maybe I'm too old but I'm not liking the setup > they made. > > So thought I would ask what is the best practice now for chunk layout. > > They created one big cooked file for dbs0 (production) and the same for > dbs1 > (test). > > On the HPUX I basically used 2GB chunks and made sure I had 1 year of free > space or more. We have twice a year Federal Loan processes that can > generate > lots of records that have a short life so sometimes need a good buffer. So > had > 24 2GB chucks. Maybe not the greatest layout but never had problems with it > since 1999 when we first setup Informix. > > To me this one big supper-sized chunk just seems a bad idea. > > Any words of wisdoms would be greatly appreciated. > > John Adamski > > Sr. Network Specialist > > Graceland University > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --94eb2c0d738e138497054b773321