views:

6

answers:

0

What happens if I set this variable to 0? What are its side effects?

I'm currently having trouble with the db.dat file, it's currently on 60 gB. Can I solve this issue setting the databaseIncrementSize to 0?

I'm currently reading this link

Data in LucidDB is stored using 32K pages in an operating system file named db.dat. Pages are allocated from that underlying random-access file. When LucidDB is first initialized 2000 pages, equivalent to 62MB, are allocated for that file. The first two pages are reserved for storing system state (e.g., checkpoint information). The two pages store identical information. By having two pages and writing them out synchronously during checkpoints, this ensures that LucidDB will always have at least one good copy of the page, in case of a system crash while in the middle of writing out one of the two pages.

The remaining pages are available for storing user-data, although there are also metadata pages sprinkled in between those user pages. As the database grows, additional new pages are allocated, by default, in blocks of 1000 pages (31MB). That value is configurable. Once additional database pages are allocated, the size of the underlying file never shrinks, even if the pages are not being used.

How can I configure the value so that the new pages are allocated in smaller blocks?