StellarSQL icon indicating copy to clipboard operation
StellarSQL copied to clipboard

Implement memory pages and write back mechanism

Open tigercosmos opened this issue 6 years ago • 1 comments

Now we use dirty property to record the status of the SQL object. The pool stores many SQL, and when the SQL is pop out or the client disconnects the server, the dirty data will write back to storage.

We should rather implement memory pages and manages the pages. Probably use memmap crate. We should also write back data as soon as possible. The time written back needs discuss.

tigercosmos avatar Jan 13 '19 13:01 tigercosmos

https://github.com/jonhoo/rust-evmap

GitHub
A lock-free, eventually consistent, concurrent multi-value map. - jonhoo/rust-evmap

tigercosmos avatar Mar 11 '19 13:03 tigercosmos