JPOX, by default, provides certain functionality. In particular circumstances some of this functionality may not be appropriate and it may be desirable to turn on or off particular features to gain more performance for the application in question. This section contains a few common tips
JPOX provides 2 PersistenceManagerFactory properties org.jpox.validateTables, org.jpox.validateConstraints that enforce strict validation of the datastore tables against the Meta-Data defined tables. This can cause performance issues at startup. In general this should be run only at schema generation, and should be turned off for production usage. Set both of these properties to false.
JPOX provides a series of identity generators (POID Generators) for generation of identity values. These can have an impact on performance depending on the choice of generator, and also on the configuration of the generator.
- The MaxPoidGenerator should not really be used for production since it makes a separate DB call for each insertion of an object. Something like SequenceTablePoidGenerator should be used instead.
- The OracleSequencePoidGenerator and PostgresqlSequencePoidGenerator allow configuration of the sequence. The default is often non-optimum. As a guide, you can try setting key-cache-size to 10 and key-increment-by to 10.
