|
From: bpcs-l-request@xxxxxxxxxxxx <bpcs-l-request@xxxxxxxxxxxx>
Subject: BPCS-L Digest, Vol 8, Issue 133
To: bpcs-l@xxxxxxxxxxxx
Date: Tuesday, July 20, 2010, 1:00 PM
Send BPCS-L mailing list submissions
to
bpcs-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help'
to
bpcs-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
bpcs-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of BPCS-L digest..."
*** NOTE: When replying to this digest message, PLEASE
remove all text unrelated to your reply and change the
subject line so it is meaningful.
Today's Topics:
1. Re: 8.3.3 MRP run time (darren@xxxxxxxxx)
2. Re: 8.3.3 MRP run time (akleier@xxxxxxxxxxxxxxxx)
----------------------------------------------------------------------
message: 1
date: Mon, 19 Jul 2010 14:04:03 -0400
from: darren@xxxxxxxxx
subject: Re: [BPCS-L] 8.3.3 MRP run time
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.
------------------------------
message: 2
date: Mon, 19 Jul 2010 14:27:56 -0400
from: akleier@xxxxxxxxxxxxxxxx
subject: Re: [BPCS-L] 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.
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/bpcs-l.
Delivered-To: akleier@xxxxxxxxxxxxxxxx
------------------------------
--
This is the BPCS ERP System (BPCS-L) digest list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/bpcs-l.
End of BPCS-L Digest, Vol 8, Issue 133
**************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
