Bitcoin Forum
April 21, 2021, 06:12:30 PM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Level DB vs VSAM KSDS  (Read 892 times)
meetreks
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
July 27, 2015, 12:12:49 PM
 #1

Hi,

Just wondering what people think about Level DB and its comparisons to VSAM KSDS files.

KSDS files are ordered in key & data value pairs same as Level Db does.

Regards,
Meetreks
"Apparently, so I am told, there exist "people" who prefer to wipe sitting down. From the front. Initial research indicates it could be up to half the population." -- benjamindees
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1619028750
Hero Member
*
Offline Offline

Posts: 1619028750

View Profile Personal Message (Offline)

Ignore
1619028750
Reply with quote  #2

1619028750
Report to moderator
1619028750
Hero Member
*
Offline Offline

Posts: 1619028750

View Profile Personal Message (Offline)

Ignore
1619028750
Reply with quote  #2

1619028750
Report to moderator
1619028750
Hero Member
*
Offline Offline

Posts: 1619028750

View Profile Personal Message (Offline)

Ignore
1619028750
Reply with quote  #2

1619028750
Report to moderator
mustyoshi
Sr. Member
****
Offline Offline

Activity: 287
Merit: 250



View Profile
July 29, 2015, 10:14:28 PM
 #2

You should create a wrapper for Level DB calls to the VSAM KSDS library and do some benchmarks.

hexafraction
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250

Tips welcomed: 1CF4GhXX1RhCaGzWztgE1YZZUcSpoqTbsJ


View Profile
July 29, 2015, 10:17:50 PM
 #3

You should create a wrapper for Level DB calls to the VSAM KSDS library and do some benchmarks.



Benchmarks alone are not sufficient. Testing failure cases such as crashes, power loss, etc and seeing how they affect the integrity of the data in overt or subtle ways is also important.

I have recently become active again after a long period of inactivity. Cryptographic proof that my account has not been compromised is available.
2112
Legendary
*
Offline Offline

Activity: 2128
Merit: 1038



View Profile
July 30, 2015, 12:46:55 AM
Last edit: July 30, 2015, 01:02:54 AM by 2112
 #4

Nobody in the core development team has any significant experience with databases.

By not providing a database abstraction layer for the various storage pools (including mempool) they can have a better grip on the whole project.

Check out the historical perspective from 3 years ago:

blah blah blah blah
Gentle reminder to the other bitcoin developers: it is generally best not to feed trolls.  Use the ignore button.

Edit: Actually I just realized that you've asked about VSAM, which would mean that you've compiled it on the (big-endian) IBM mainframe. Does it work at all?

Please comment, critique, criticize or ridicule BIP 2112: https://bitcointalk.org/index.php?topic=54382.0
Long-term mining prognosis: https://bitcointalk.org/index.php?topic=91101.0
jonas.schnelli
Member
**
Offline Offline

Activity: 66
Merit: 10

bitcoin core contributor


View Profile WWW
July 30, 2015, 08:06:27 AM
 #5

Nobody in the core development team has any significant experience with databases.
By not providing a database abstraction layer for the various storage pools (including mempool) they can have a better grip on the whole project.

Would it make sense to store the mempool on-disk?

--snip--

LevelDB (kv store) seems pretty much the thing we need for bitcoin-core (there is no need for extensiv querying if you don't want to run a block explorer). What alternatives would you propose today? Would it be worth implementing (balance between (implementation-time+risks <==> benefits-of-a-new-database)? How would you handle migration, testing on serval filesystems?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!