Keys storage not grow, they are overriding on an update, values override too if size of old value is sufficient
If no - it will grow. I have plans to add compaction on backup in future. Right now backup may be implemented in three command (sets(gets(keys()))) > On 18 Apr 2018, at 11:31, Sokolov Yura <[email protected]> wrote: > > How it is compacted? > Values will be updated and deleted, storage file will grow. How garbage will > be collected? > > вторник, 17 апреля 2018 г., 14:37:27 UTC+3 пользователь vadim kulibaba > написал: > Hi Everyone, > > I finished simple and effective key/value store with nice api: > https://github.com/recoilme/slowpoke <https://github.com/recoilme/slowpoke> > > The performance was not a target of this database but it performs well and > not so slow as i expected. It just stores values in files and keys with value > addresses in memory, with persistence. No LSM-tree, no BTree, no mmap, just > standard library (hash table+slice in goroutine). > > Let me know what you think! > > -- > You received this message because you are subscribed to a topic in the Google > Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/eGW7eDvdnBw/unsubscribe > <https://groups.google.com/d/topic/golang-nuts/eGW7eDvdnBw/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
