Pro*C Size/Speed issues

Hi,

Platform: VAX/VMS v5.5-2, VAX C

          Oracle RDBMS 7.0.15.4
          Pro*C 1.5.6.2.0

I've got a Pro*C program. It was a C program, to which I added only as much as necessary to logon to Oracle. There will be much more to come later, but for now, it just logs on. The .exe jumped from 171 blocks to 1735 blocks. The whole program slowed down, probably due to page faulting.

What are my options now? What is the extra size, a map of the SGA? Note: on a machine with a considerably smaller SGA, the executable is only 797 blocks.

I've written in Pro*C before. That's no problem. This is the first time, however, that I have had an opportunity to see the difference between "with" and "without" Oracle access in the same program.

The previous stuff has been for batch use, this one is for interactive use. I need to be concerned with performance issues this time around.

I'd like to see a bit of discussion on the topic if anyone else is interested.

For example, I'm using dynamic memory allocation to deal with data that's coming in from flat files. Would I be any better off if I pre-allocate a large static array?

What can I do as the programmer to make this situation be the best that it can possibly be?

If I knew how, I could put the static data into shared memory and read it from there. That would be new ground for me. How difficult is it?

Any suggestions out there?

Thanks,

Jennifer R. Amon            PHONE: (216) 775-6987
Houck Computing Center        FAX: (216) 775-8573
Oberlin College
Oberlin, OH 44074        INTERNET: bamon_at_ocvaxc.cc.oberlin.edu


_____________________________________________________________________