RE: Subsystems and ODP - answer to Wilt, Charles

Charles

You also probably need to clear the data from memory between runs to get a more valid test - you can do this with the SETOBJACC command - there is a special value for clearing the data for a file. You may be getting the benefit of data already in memory on the second and subsequent runs.

Vern

-------------- Original message --------------
From: "Charles St-Laurent" <dringpiece@xxxxxxxxxxx>

Hi!

I looked at the data performance analysis tool that is provided in iSeries
Navigator when I launched the process. The big performance loss was when I
have to open the database files for the first time. So I supposed that if I
can keep these files open between calls, the entire process would be shorter
than now. That's why the idea to have a server job with a specific
activation group and many children threads sharing the same activation group
appeared to me to be the best way to solve our performance loss. Once opened
in the activation group, the ODPs will stay opened and will be re-used by
subsequent requests.

I tested shared ODP locally on my user by calling the process interactively
without reclaiming the activation group ressources between calls. The first
time I launched the process, I got the result after 50 seconds, probably
because it had to open files for the first time. Then, all my subsequent
calls took an average of 5 - 10 seconds for exactly the same request.


Charles St-Laurent
Consultant Berco
Technologies
Industrielle Alliance, Assurance auto et habitation
Téléphone : 418 650-4600, poste 3216
Sans frais : 1 800 463-4382
Télécopieur : 418 650-4612
Sans frais : 1 877 650-4612
Courriel : charles.st-laurent@xxxxxxx
www.inalco.com/assurancegenerale


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