Why is this small database creating such a big page file and
behaving so slowly? I had specified a big node number (10e6),
but I have since compressed node numbers and saved the database.

The problem stems from the very large index in the database that points to the nodes within the database. This applies to large element numbers as well.

When entity numbers are compressed with NUMCMP, the program does not "shrink" back the indices. It writes out the size used for the indices on the database file so that it is only when the database is resumed that the database memory needed
to store the large index is accessed, resulting in the large page file and slow behavior.

At 9.0, after NUMCMP is used to compress entity numbers, the program will reduce the size of the index to match the current max entity number. [Ref: Defect 22735]

Show Form
No comments yet. Be the first to add a comment!