Open auxten opened 9 months ago
All issues with label https://github.com/chdb-io/chdb/labels/Session is related to this feature
Here is the rough plan:
BackgroundSchedulePool
and all kinds of Context
👋 @auxten
Would it also support stale parts cleanup https://github.com/chdb-io/chdb/issues/107?
And, in general, full use of MegreTrees (writing, parallel reading, etc.) https://github.com/orgs/chdb-io/discussions/210#discussioncomment-8863924
👋 @auxten
Would it also support stale parts cleanup https://github.com/chdb-io/chdb/issues/107?
Yes, I think so
👋 @auxten Would it also support stale parts cleanup #107?
Yes, I think so
If it is not possible to merge partitions, each append operation will cause the partition to keep expanding.
👋 @auxten Would it also support stale parts cleanup #107?
Yes, I think so
If it is not possible to merge partitions, each append operation will cause the partition to keep expanding.
Yes, It's a serious problem in current impl. In this new impl, there will be some background threads doing the merge work periodically.
Current chDB(till v2.0.2) relys on temp disk storage to keep the session data. Everytime
session.query
runs almost everything in memory will be recreated and reinit which caused a lot of state problems like:Also some feature implemented and bugs walked around before also need a better way to fix:
133
176
207
Some chDB contributor also gave a try to make session better:
The good part are:
query
function call, Performance should be much better than current implementation