Re: Insert and Long Names

How are you doing the inserts?

One row at a time in a loop?

That might explain why it has to resolve the name each time.

I know single row inserts are expensive, but I wouldn't expect the single
row insert using the short name to be that much faster.

Ok..just read Luis' post...interesting...though it doesn't mention long
column names, just long object names.

Charles

On Mon, Dec 28, 2015 at 11:42 AM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

We are doing data conversion of large amount of data and we are seeing very
interesting behavior if we are using long names when we do the writes.

All the tables are defined using DDL using both long names and short. If we
write to the tables using long names we see CPU shot straight up and
running iDoctor reveals that each write seems to be making function calls
to an internal system API that translates the long name to the short.

It would make sense to me that it would do this once but for every records?

To wirte 50,000 records using long names takes 8 seconds and 2 seconds
using short names. We have a very big machine.

Turn on Job Watcher and looked at CPU consumption. Huge spike straight up,
straight across and down for long names. Doesn’t even register for short
names.


Anybody else run into this?

We are V7R2.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.