Re: 8.3.3 MRP run time

In our 8.3.3 LX environment we used the STRDBMON command to monitor
database indexes used and created during specific processes such as MRP or
the entire system. Output the results to a file then query the file for
index advised field qqidxa = "Y". The fileds to look at are qqtln, qqtfn,
qqifnm, qqidxa, qqidxd. This tells you the system is building indexes
instead of using ones supplied by Infor. We then used the sql CREATE
INDEX command to create the advised index against the LX file in files
library. The creation of custom indexes in our environment improved the
speed of many processes, not just MRP. We have build well over 50 indexes
against many commonly used LX files.

Hope this helps.

Tony Kleier
Robbins, Inc.
Office: 513-619-5957
akleier@xxxxxxxxxxxxxxxx
www.robbinsfloor.com




From: darren@xxxxxxxxx
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Date: 07/19/2010 02:08 PM
Subject: Re: [BPCS-L] 8.3.3 MRP run time
Sent by: bpcs-l-bounces+akleier=robbinsfloor.com@xxxxxxxxxxxx



Here is an example of performance:

Running MRP500 over one particular facility in 405CD is 149 seconds.
Similar data, converted to LX 8.3.3 runs in 349 seconds for that facility.
All facilities process in about 12 minutes in 405CD. For LX 8.3.3 it
takes
about 45 minutes.

The issue we have is that we currently run MRP500 for all facilities,
manipulate some data, and run it again. We then run DRP500, and MRP600.
This adds up to 45 minutes in 405. This is tolerable. In LX8.3.3, this
same process takes a little over 2.5 hours.

I suspect a poor implementation of SQL statements in place of traditional
I/O, but if anyone has found a turbo booster for MRP500, I would love to
hear about it.