Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incremental DB file growth for Windows

See original GitHub issue

I’m currently using lmdbjava 0.6.0 which uses LMDB 0.9.19 (retrieved via Meta.version()).

When using Linux setting a large map size is no problem: The database file grows with the size of the database. This is convenient as I can just use a very large value and I don’t have to care about database resizing.

When using Windows (I’m using Windows 7) the database file size is always the same as the mapping size. E.g. when I set a map size of 100GB then the file size will be 100GB, too.

The LMDB inventor says this behavior has been changed (ITS#8324). The corresponding commit seems to be

fb5a768 Mon Nov 30 19:46:19 2015 ITS#8324 incremental DB file growth for Windows

which is from Nov. 30, 2016 and it should be included in LMDB 0.9.19.

However, the file size behavior under Windows still persists with lmdbjava 0.6.0. So I’m wondering:

Did I misunderstand what ITS#8324 is supposed to do?
Did lmdbjava bundle the wrong LMDB version?
Or does the issue still exist in LMDB?

Any ideas?

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:13 (4 by maintainers)

Top GitHub Comments

1reaction

benalexaucommented, Sep 8, 2017

LmdbJava bundles LMDB version 0.19.1, which was built from the tag LMDB_0.9.19, commit 14cff072ec29f48093a9d40cc79934cf5376af4a.

While ITS#8324 shows up in several commits as per https://github.com/LMDB/lmdb/search?q=“ITS%238324”&type=Commits&utf8=✓ these do not appear to be included in the above tag or change log (or at least I can’t see that with a quick search).

I see that LMDB 0.9.21 is now out, so I will log a new ticket to get LmdbJava updated to that version and we can see if that included the changes.

0reactions

vladpcommented, Jul 22, 2018

It seems like on Windows platform, this still continuous to be a limitation.

“… When using Windows (I’m using Windows 7) the database file size is always the same as the mapping size. E.g. when I set a map size of 100GB then the file size will be 100GB, too. …”

I am on windows 10 , using LMDBJava 0.6.1. Are there workaround, by any chance, developed for this windows-only issue?

I am storing images in LMDB (of over 3mb in size each) – so I am reaching this problem rather quickly.

thx

Top Results From Across the Web

SQL Server Database Growth and Autogrowth Settings

Each database file that is associated with your database has an auto-growth setting. There are three different settings you can use to identify ......

Get details of SQL Server Database Growth and Shrink Events

This article explores SQL Server database auto-growth and shrink events along with capturing ... Auto Growth File size increment: 100 GB.

Increase the Size of a Database - SQL Server | Microsoft Learn

Expand Databases, right-click the database to increase, and then click Properties. In Database Properties, select the Files page. To increase ...

Considerations for the autogrow and autoshrink - SQL Server

Consider setting databases to a required size and pre-grow them. Leave the unused space in the database files if you think the application ......

What is the best practice for database file growth configuration?

I would recommend look at the your data growth and go with large increment possible. I wouldnot going to recommend 64 MB. Important...