Skip to content
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.

Implement memory pages and write back mechanism #24

Open
tigercosmos opened this issue Jan 13, 2019 · 1 comment
Open

Implement memory pages and write back mechanism #24

tigercosmos opened this issue Jan 13, 2019 · 1 comment
Labels
E-Hard enhancement New feature or request todo 🗒️

Comments

@tigercosmos
Copy link
Member

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
Copy link
Member Author

tigercosmos commented Mar 11, 2019 •
edited by unfurl-links bot
Loading

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

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
E-Hard enhancement New feature or request todo 🗒️
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tigercosmos