{"id":100127,"date":"2021-05-09T22:23:13","date_gmt":"2021-05-09T20:23:13","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-vysokoproizvoditelnoj-vstraivaemoj-subd-libmdbx-0-10"},"modified":"2021-05-09T22:23:13","modified_gmt":"2021-05-09T20:23:13","slug":"vypusk-vysokoproizvoditelnoj-vstraivaemoj-subd-libmdbx-0-10","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-vysokoproizvoditelnoj-vstraivaemoj-subd-libmdbx-0-10","title":{"rendered":"Release of the high-performance embedded DBMS libmdbx 0.10.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After three months of development, the release of the libmdbx 0.10.0 (MDBX) library took place, featuring a high-performance, compact embedded key-value database. The libmdbx code is distributed under the OpenLDAP Public License. libmdbx is a thorough redesign of the LMDB database management system and, according to the developers, surpasses its predecessor in reliability, feature set, and performance. It is claimed that libmdbx is up to 20% faster than LMDB in CRUD scenarios and up to 30% faster if internal checks in libmdbx are disabled to levels comparable to LMDB. <\/p>\n
Libmdbx offers ACID compliance, strict change serialization, and non-blocking reads, with linear scaling across CPU cores. Great attention is paid to code quality, stable API operation, testing, and automated checks in libmdbx. It supports auto-compaction, automatic database size management, a single database format for both 32-bit and 64-bit builds, and sampling volume estimation for range queries. A database structure integrity check utility with some recovery options is included. Since 2016, the project has been funded by Positive Technologies, and since 2017, it has been used in its products; the sanctions imposed by the U.S. government against Positive Technologies have no noticeable impact. <\/p>\n
The main innovations, improvements, and fixes added since the last release include: <\/p>\n
\n
Bindings for Ruby by Mahlon E. Smith and a trial version of bindings for Python by Noel Kuntze are available, and the bindings for GoLang by Alexey Sharov have been updated.\n
For the \"MDBX_WRITEMAP\" mode, when database data is modified directly in RAM, a \"transparent spill\" to disk for the modified database pages has been implemented. Now, after each operation, such pages are immediately fully ready to be written to disk, allowing the OS kernel to flush the modified pages to disk independently, and the transaction commit will not require their modification. As a result, in high-load scenarios with insufficient RAM, the number of disk operations can be reduced by up to 50%.\n
Implemented the replacement of long-unused shadow copies of modified pages, prioritizing the replacement of pages with large\/long values that are, in the overwhelming majority of scenarios, modified only once per transaction. As a result, disk I\/O is reduced, thereby increasing performance in scenarios with very large transactions.\n
A \"smart\" page splitting mode during key insertion has been implemented. Now, when inserting ordered sequences, complete filling of the pages is automatically ensured, while in other cases, more optimal tree balancing is achieved. As a result, on average, database pages are filled more efficiently, and the B-tree is more balanced, positively affecting performance.\n
Statistics for page operations have been added, allowing for precise assessment of the cost of modifying operations on the database.\n
More than a dozen issues and bugs have been resolved, including: problems with building using MinGW, using `std::filesystem::path` on iOS <= 13.0, building targeting older versions of Windows, etc.\n
A total of over 200 changes have been made in 66 files, with approximately 6500 lines added and about 4500 removed. <\/ul>\n
It is worth highlighting the selection of the Turbo-Geth project (turbo-fork of Go-Ethereum) to use libmdbx as the new storage backend and thank the project team (especially Alexey Sharov, Artem Vorotnikov, and Alexey Akhunov) for their significant help in testing under extreme usage scenarios. In particular, a defect in prefetching\/caching management was identified and eliminated, which previously led to performance degradation in complex-to-reproduce scenarios with large databases. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"