Dear Ingres User,

Greetings from Shakthi one of the ingres user.

I am using Sun Enterprise Server E250 with 1GB Ram Hardware.

The systems and database is working fine. But Suppose i

make exe file (imageapp) it take very large time.

At the time installing it took very few seconds per frame.

Now It will take some minite per frames.

Any ideas or solutions to improve the speed?

Expecting your's valueble replays...

Advance Thanks & Regards
Shakthi
Chettinad Cements
India

Hi Shakthi,

Try the following.
1. Edit the file $II_SYSTEM/ingres/files/dictfiles/cor02min.mfy
At the end of this file, simply ADD the following index creation. Do
NOT remove anything else.

create index ii_object_name_index on ii_objects (
object_name, object_class, object_owner, object_id
)
with key=(object_name, object_class), structure=btree


While your in this file you might like to change all cbtree references to
btree.

2. Run a sysmod on the database. It will now use the new definitions you
have put in this file.

This should speed up the compilations.

Martin Bowes

--
Is it just me, or is there a dark undercurrent beneath the fluff of
'Sabrina the Teenage Witch':
Sabrina about to be thrown to the Lions...
Aunt Zelda - Don't let them smell your fear.
Sabrina - Oh? So bravery will mask the smell of my succulent flesh?

I would also add the following index :

create index ii_abfobjects_index on ii_abfobjects
(object_id)
with structure = btree


"Martin Bowes" <bowes (AT) bucket (DOT) its.unimelb.edu.au> wrote

Hi Colin et al,

This has been interesting....

Don't add the create of ii_abfobjects_index to the file cor02min.mfy. You
are better off adding it to the file ad103min.mfy as its in that file
(amongst others!) that the modify of ii_abfobjects occurs.

However...

A lot of this depends on exactly what you call when you do a sysmod and
(I suspect) on how your system is configured.

eg. Check the difference in output between:
sysmod bowtest -fwindows_4gl and sysmod bowtest

In the former, the order of processing is: APPLICATION_DEVELOPMENT_2
version 1, APPLICATION_DEVELOPMENT_1 version 3 and finally CORE
version 2. ie files ad201min.mfy, ad103min.mfy and finally
cor02min.mfy.

In the latter, the order of processing is: CORE version 2,
APPLICATION_DEVELOPMENT_1 version 4, APPLICATION_DEVELOPMENT_1 version
3, APPLICATION_DEVELOPMENT_2 version 1 and finally
APPLICATION_DEVELOPMENT_3 version 1. ie files cor02min.mfy,
ad104min.mfy, ad103min.mfy, ad201min.mfy, and finally ad301min.mfy.

So if you just 'sysmod bowtest' then any index create in cor02min.mfy is
removed by the modify of ii_abfobjects in ad104min.mfy and again in
ad103min.mfy!

Note that ii_abfobjects is modified in the files: ad101min.mfy,
ad102min.mfy, ad103min.mfy, ad104min.mfy. BTW ad101 will make it unique
keys!

All these files have been created to allow the different flag options to
sysmod to be customised, hence there is some repitition.

eg. sysmod bowtest -fingres uses cor02min.mfy and ad104min.mfy

sysmod bowtest -fingres/dbd uses cor02min.mfy only

sysmod bowtest -fvision uses cor02min.mfy, ad104min.mfy and
ad301min.mfy.

So in short, if you want to add this index create to your catalogs then
you'll have to add it to at least ad104min.mfy and ad103min.mfy.
There is no need to add it to cor02min.mfy as the action of that file will
not remodify ii_abfobjects. Furthermore, if the index exists then an
index create in cor02min.mfy will cause the sysmod to fail.

Marty Bowes


--
Random Titus Quote #2:
I don't fail. I succeed at finding what doesn't work.