Keywords: derby.storage.pageSize, Page size, performance implications of

# Tune the size of database pages

Stick with 4K as the page size (the default, and the size operating systems use) unless:

- You are storing large objects.
- You have very large tables (over 10,000 rows).

  For very large tables, large pages reduces the number of I/Os required.

- For read-only applications, use a large page size (for example, 32K) with a pageReservedSpace of 0.

You might need to experiment with page size to find out what works best for your application and database.

- Performance trade-offs of large pages

Parent topic: The tips
Related concepts
Use prepared statements with substitution parameters
Create indexes, and make sure they are being used
Increase the size of the data page cache
Avoid expensive queries
Use the appropriate getXXX and setXXX methods for the type
Tune database booting/class loading
Avoid inserts in autocommit mode if possible