lmdb - npm Package Compare versions

Comparing version 1.6.2 to 1.6.3

index.js

		@@ -1102,3 +1102,3 @@ const { sync: mkdirpSync } = require('mkdirp')
		backup(path) {
		return new Promise((resolve, reject) => env.copy(path, true, (error) => {
		return new Promise((resolve, reject) => env.copy(path, false, (error) => {
		if (error) {
		@@ -1105,0 +1105,0 @@ reject(error)

package.json

		{
		"name": "lmdb",
		"author": "Kris Zyp",
		"version": "1.6.2",
		"version": "1.6.3",
		"description": "Simple, efficient, scalable data store wrapper for LMDB",
		@@ -6,0 +6,0 @@ "license": "MIT",

README.md

		@@ -349,8 +349,8 @@ [![license](https://img.shields.io/badge/license-MIT-brightgreen)](LICENSE)
		#### LMDB Flags
		In addition, the following options map to LMDB's env flags, <a href="http://www.lmdb.tech/doc/group__mdb.html">described here</a>. None of these need to be set, the defaults can always be used, and only `noMemInit` is recommended, but others are available for boosting performance:
		* `noMemInit` - This provides a small performance boost (when not using useWritemap) for writes, by skipping zero'ing out malloc'ed data, but can leave application data in unused portions of the database.
		In addition, the following options map to LMDB's env flags, <a href="http://www.lmdb.tech/doc/group__mdb.html">described here</a>. None of these need to be set, the defaults can always be used and are generally recommended, but these are available for various needs and performance optimizations:
		* `noSync` - Doesn't sync the data to disk. This can be useful for temporary databases where durability/integrity is not necessary, and can significantly improve write performance that is I/O bound. We discourage this flag for data that needs integrity and durability in storage, since it can result in data loss/corruption if the computer crashes.
		* `noMemInit` - This provides a small performance boost for writes, by skipping zero'ing out malloc'ed data, but can leave application data in unused portions of the database. If you do not need to worry about unauthorized access to the db files themselves, this is recommended.
		* `remapChunks` - This a flag to specify if dynamic memory mapping should be used. Enabling this generally makes read operations a little bit slower, but frees up more mapped memory, making it friendlier to other applications. This is enabled by default on 32-bit operating systems (which require this to go beyond 4GB database size) if `mapSize` is not specified, otherwise it is disabled by default.
		* `mapSize` - This can be used to specify the initial amount of how much virtual memory address space (in bytes) to allocate for mapping to the database files. Setting a map size will typically disable `remapChunks` by default unless the size is larger than appropriate for the OS. Different OSes have different allocation limits.
		* `noSync` - Doesn't sync the data to disk. This can be useful for temporary databases where durability/integrity is not necessary, and can significantly improve write performance that is I/O bound. We discourage this flag for data that needs integrity and durability in storage, since it can result in data corruption. For situations where `noSync` is appropriate, it is often useful to combine with `useWritemap` for further performance benefits.
		* `useWritemap` - Use writemaps, this improves performance by reducing malloc calls and file writes, but can increase risk of a stray pointer corrupting data. This is currently disabled on Windows if not combined with `noSync`. Combined with `noSync`, normal reads/writes/transactions involve virtually zero explicit I/O calls, only modifications to memory maps that the OS persists when convenient.
		* `useWritemap` - Use writemaps, this can improve performance by reducing malloc calls and file writes, but can increase risk of a stray pointer corrupting data, and may be slower on Windows. Combined with `noSync`, normal reads/writes/transactions involve virtually zero explicit I/O calls, only modifications to memory maps that the OS persists when convenient, which may be beneficial.
		* `noMetaSync` - This isn't as dangerous as `noSync`, but doesn't improve performance much either.
		@@ -357,0 +357,0 @@ * `pageSize` - This changes the page size of the database. This is 4096 by default, and the default generally has the best performance since it aligns with normal OS page size.

dependencies/lmdb/libraries/liblmdb/mdb.c