What is recommended configuration to use pebble as queue?

[kanekv]

E.g. what would be an equivalent of this: https://github.com/facebook/rocksdb/wiki/Implement-Queue-Service-Using-RocksDB

Values in my case should be mostly short-lived, and this strictly applies:

In these services, from each queue, new items are added with a higher sequence ID
 and removed from the smallest sequence ID. 
 Users usually read from a queue in sequence ID increasing order.

Also it will delete read items immediately.

Jira issue: PEBBLE-300

[jbowens]

Much of the advice in the RocksDB document applies to Pebble as well. The 'Old Item Deletion Problem' is good advice.

On the subject of 'Reclaiming space of deleted items faster,' you may want to use DeleteRange to batch delete swaths of the tail of the queue, if you can delay the deletion. Wide range deletion tombstones are cheaper to skip over than many individual point tombstones.

[kanekv]

@jbowens what would be a good configuration for the base level and memtables? I assume it will benefit to make them as big as possible if all items are relatively short-lived?