Implement Storage Engine about agatedb HOT 5 OPEN

@Fullstop000 Do you have an interest to participate in this work?

from agatedb.

@Fullstop000 Do you have an interest to participate in this work?

Sure :)

from agatedb.

@Fullstop000 Do you have an interest to participate in this work?

mee too :)

from agatedb.

@Fullstop000 Do you have an interest to participate in this work?

mee too :)

I will post a future roadmap soon, and we may discuss what to do next later :)

from agatedb.

@Fullstop000 Do you have an interest to participate in this work?

mee too :)

I think the critical missing pieces are:

• vLog GC
• block + index cache and compression

And there are a lot of small things for improvement, for example:

• use thread pool for SST merging
• reduce vLog lock contention
• and so on...

And finally a big design decision for the future of AgateDB:

• Do we really need to implement MVCC capabilities of Badger? It seems that a KV store with the snapshot capability is enough for TiKV.

After all, there is no clear development plan for AgateDB for now. If you have any idea or question, feel free to ping @skyzh on TiKV Slack. cc @leemaster

from agatedb.