× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: RPG IV Performance
  • From: "Mark A. Manske" <mmanske@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 19 Jan 2001 08:49:25 -0600
  • Importance: Normal

IMHO I would say that these people are looking for a way to avoid coding in
RPGIV by saying these things -
is there a true issue, I really do not know how the bare metal code works;
but keep the following in mind -

A trigger program against a file, regardless of "language used" is executed
at the OS level when something
happens to the file as you have specified (IE: record added, changed,
deleted; and a time to perform the
trigger program - before, after the file operation) it does not "run in the
back ground" it gets called
from the OS because of the file operation; similar to exit programs for say
FTP, these are not running all
the time, they get called based on the file, not the user.

As for program size - we are no longer in the S/34 world (been there) where
we could only go up to a 64K
program and had to be "creative" in keeping size down.  Unless you have an
undersized AS/400-this is a
mute point, and if you do, you most likely have many other issues with
performance to worry about.


I know there are others out here that can better explain the "nuts and
bolts"; but basically it sounds
like they are blowing smoke.

HTH
Mark A. Manske
[mailto:mmanske@minter-weisman.com]
Sr. Project Lead
Minter-Weisman




-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of Lisa.Abney@universalflavors.com
Sent: Friday, January 19, 2001 7:07 AM
To: RPG400-L@midrange.com
Subject: RPG IV Performance




Hi all!  I've just heard some rather negative performance things on RPG IV,
and
wonder if anyone can give me some feedback on how true this might be.

We're working with a consulting company who is doing some performance
analysis
on some of our programs.  They seem very knowledgeable, and I have a lot of
confidence in what they've done up until now.  However, today they were
showing
us a mock-up of a trigger program they want to use.  As they explained it,
this
trigger program will be constantly running in the background for every user
on
the system to monitor changes to two files, and will feed data to a dataque.
The program they showed me was written in RPGIII, and I made my usual
request to
an outside contractor that this be done in RPGIV.  His response was "Sure,
if
you want the program size to be 5 - 10 times the size of an RPGIII program."
When I asked him to explain that, he only said that, in his experience, this
is
always true, and that it would have a very negative performance.  I even
mentioned removing observability (not that I really understand what that
means,
but I just read something the other day about that being a way to reduce
program
size!), and he said that might move it down to 3 - 5 times the size of an
equivalent RPGIII program.  The program will only be about 50 - 100 lines of
code.

Can someone explain if this is true, and, if so, why?  And, if true, what
does
this really mean from a performance standpoint?

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.