Making BPCS + ERP LX run faster / response time information

<vendor>



What Ronnie said about BPCS' v6.x "speed problem" is true ... and it's true
for all the v8.x releases too. That has been decisively fixed at other
places without buying a bigger machine (and without convincing INFOR to give
you an affordable price for a new key).



Try archiving first:
www.unbeatenpath.com/software/locksmith/archiving.pdf



Then read this about tuning:
www.unbeatenpath.com/up-a-notch/adrenaline/optimize.pdf



Archiving and tuning are good ideas for any BPCS or ERP LX user. When the
files get too big, user productivity suffers. Some "next screen"
presentations trigger an enormous load of background processing on one or
more of those big files. Please contact us off-line for specific examples.





Technical Insight:

At v4.05CD, all the logical files were already built (SQL was not available).
Starting at v6.x, a subset of the indexes were delivered with vanilla code.
This saves some time in most programs because there are less logical files to
dynamically maintain. But, when SQL launches an on-the-fly creation of an
unavailable index, big files greatly exacerbate the machine resource hit. (By
the way ... indexes created on-the-fly are dumped ..... so the next time that
the same program runs, the SQL index-building process is repeated.)



Merry Christmas,

Milt Habeck

Unbeaten Path

(888) 874-8008

+262-681-3151

<mailto:mhabeck@xxxxxxxxxx> mhabeck@xxxxxxxxxx

</vendor>









+++++++ +++++++ +++++++ +++++++ +++++++ +++++++

From: Ronnie lim

Sent: Tuesday, December 07, 2010 7:43 PM

To: bpcs-l@xxxxxxxxxxxx

Subject: Re: [BPCS-L] BPCS-L Digest, Vol 8, Issue 218



upgrading from 4.05cd to v6.1.



When I was working for Volex, the Volex bpcs's expert Elaine Rabitor base in
Boston did the migration.

[BPCS v]6.1 is very slow due to the many sql used. need to observe and
rebuild the indexes so that it did not rebuild every time the sql us
executed.



buy more ram and bue a much larger cpw then needed will save the process
speed problem.



best of luck.

ron