Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
dgraph
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Mirror
dgraph
Commits
da5b6cb4
Commit
da5b6cb4
authored
9 years ago
by
Manish R Jain
Browse files
Options
Downloads
Patches
Plain Diff
No BoltDB for me!
parent
04bad0eb
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
store/README.md
+4
-0
4 additions, 0 deletions
store/README.md
with
4 additions
and
0 deletions
store/README.md
+
4
−
0
View file @
da5b6cb4
...
...
@@ -84,3 +84,7 @@ many writes get commited by the end user.
Hence, BoltDB is a better choice. It performs better for reads/seeks, despite DGraph needing
a value copy. Writes are somewhat slower, but that shouldn't be a problem because of the
above mentioned reasons.
**Update**
: Just realized that BoltDB only allows a SINGLE writer at any point in time.
This is equivalent to a global mutex lock. That'd essentially kill DGraph's performance. So,
BoltDB is out!
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment