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.

Sign up for GitHub

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

Update compaction.md #661

Merged
merged 1 commit into from
Sep 2, 2021
Merged

Update compaction.md #661

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs-2.0/8.service-tuning/compaction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,13 +60,17 @@ These are some operation suggestions to keep Nebula Graph performing well.
## FAQ

Q: Can I do full compactions for multiple graph spaces at the same time?

A: Yes, you can. But the IO is much larger at this time.

Q: How much time does it take for full compactions?

A: When `rate_limit` is set to `20`, you can estimate the full compaction time by dividing the hard disk usage by the `rate_limit`. If you do not set the `rate_limit` value, the empirical value is around 50 MB/s.

Q: Can I modify `--rate_limit` dynamically?

A: No, you cannot.

Q: Can I stop a full compaction after it starts?

A: No you cannot. When you start a full compaction, you have to wait till it is done. This is the limitation of RocksDB.