Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Friday September 06 2019, @01:41AM   Printer-friendly

Samsung Announces Standards-Compliant Key-Value SSD Prototype

Samsung has announced a new prototype key-value SSD that is compatible with the first industry standard API for key-value storage devices. Earlier this year, the Object Drives working group of Storage Networking Industry Association (SNIA) published version 1.0 of the Key Value Storage API Specification. Samsung has added support for this new API to their ongoing key-value SSD project.

Most hard drives and SSDs expose their storage capacity through a block storage interface, where the drive stores blocks of a fixed size (typically 512 bytes or 4kB) and they are identified by Logical Block Addresses that are usually 48 or 64 bits. Key-value drives extend that model so that a drive can support variable-sized keys instead of fixed-sized LBAs, and variable-sized values instead of fixed 512B or 4kB blocks. This allows a key-value drive to be used more or less as a drop-in replacement for software key-value databases like RocksDB, and as a backend for applications built atop key-value databases.

Key-value SSDs have the potential to offload significant work from a server's CPUs when used to replace a software-based key-value database. More importantly, moving the key-value interface into the SSD itself means it can be tightly integrated with the SSD's flash translation layer, cutting out the overhead of emulating a block storage device and layering a variable-sized storage system on top of that. This means key-value SSDs can operate with much lower write amplification and higher performance than software key-value databases, with only one layer of garbage collection in the stack instead of one in the SSD and one in the database.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Friday September 06 2019, @04:05PM (1 child)

    by Anonymous Coward on Friday September 06 2019, @04:05PM (#890579)

    Also, it's posted by janrinok, so...

  • (Score: 3, Interesting) by DannyB on Friday September 06 2019, @04:55PM

    by DannyB (5839) Subscriber Badge on Friday September 06 2019, @04:55PM (#890609) Journal

    <no-sarcasm>
    I did notice who it was posted by. But the post seemed entirely reasonable.

    All of the posts seem to be missing a department.
    </no-sarcasm>

    Perhaps there is some hack or malware that has stolen all of the departments and holding them for ransom?

    --
    People today are educated enough to repeat what they are taught but not to question what they are taught.