Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FlyDB optimization problem #187

Open
sjcsjc123 opened this issue Jul 10, 2023 · 2 comments
Open

FlyDB optimization problem #187

sjcsjc123 opened this issue Jul 10, 2023 · 2 comments
Labels
discussion The issue need discuss question Further information is requested

Comments

@sjcsjc123
Copy link
Member

In order to improve the throughput of FlyDB, we have the following options:

  1. WAL logging operation, using memory read/write key-value and asynchronous drop disk

  2. Introduce message queues, hand over disk drop operations to kafka or mq, and the main process only performs memory reads and writes

  3. Enable multiple processes in the background, pass in corresponding processes based on the key, execute data drop operations in the processes, and the main process only performs memory read and write operations

  4. If a certain monitoring mechanism is adopted and the asynchronous disk drop is unsuccessful, can a notification be sent to the client before the machine goes offline.

All of the above will have Big data loss status when the machine is offline instantly. If Kafka is deployed in other nodes, the loss will be smaller, but the operation is relatively more complex.

@sjcsjc123 sjcsjc123 added discussion The issue need discuss question Further information is requested labels Jul 10, 2023
@qishenonly
Copy link
Member

good issue!

@qishenonly
Copy link
Member

In addition, we are talking about improving throughput here in the case of single machine optimization. We need to optimize single-threaded read and write so that it has better read and write performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion The issue need discuss question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants