Re: perfomance question -- MIDRANGE-L

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
For performance avoid SQL?  We have a gent here who is no big fan of SQL.
He ran some extensive checking, with blocking and all sorts of options. He
found the performance of SQL better.  (It just wasn't better enough to get
him to use it all the time.)

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Vernon Hamberg <vhamberg@attbi.com>
Sent by: midrange-l-admin@midrange.com
10/12/2002 09:41 AM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: perfomance question


Heba

I/O is the main bottleneck on the 400. One thing that can help is to
change
unused logical files to MAINT(*DLY). If you have a lot of logical files,
this will reduce I/O needed to also write to these logical files. When the
run is over, restore the settings.

This technique cannot be used on uniquely keyed logical files.

Having multiple jobs could help. Depends - do you have multiple
processors?
Even just more tasks will maybe take more CPU, while putting the I/O
requests out there. Very generally, you want to use all the CPU you can
while waiting for I/O.

Is the 3rd-party module part of a package? Do you have any control over
what it does, or how? If it's a utility, maybe you're better off rolling
your own.

For max performance, generally avoid SQL - too much overhead - and go for
native record I/O. SQL is convenient for development but can be slower.

Vern

At 12:32 PM 10/12/02 +0000, you wrote:
>Hi All,
>
>I have a performance question, one of our interface systems should put
put a
>large number of transactions into the as/400 machine and these
transactions
>should be processed within a certain limit of time.
>
>what we have developed here in-house is just a program that runs as a
>prestarted job every 30min, this program calls another third party module
to
>record the transactions...there are some cases that we need to performa
lot
>of payment transactions(at the end of month for example) and due to this
>third party module takes a considerable time because it writes a lot of
>records in many files we have a performance slow down due to the IO.
>
>I am thinking about converting the prestart job to a DB trigger...
>else can we do? If I spawn 4 jobs instead of one to process the payment
does
>it have any positive effect? Any H/W or S/W recommendations to speed up
the
>processing?
>
>Thanks in advance for any help
>Heba
>
>
>
>
>
>
>
>_________________________________________________________________
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.