Evaluating memgraph #1263
Merged
Evaluating memgraph #1263
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Josipmrden
added
the
priority: medium (missing info)
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
matea16
requested changes
Apr 25, 2025
| - Memgraph in cyber security use cases | ||
| - Memgraph in fraud detection use cases | ||
|
|
||
|
|
Contributor
There was a problem hiding this comment.
Add the callout "If you’d like to help us prioritize this content" here instead at the end of the page
|
|
||
| # Benchmarking Memgraph against others | ||
|
|
||
| ## mgbench - framework for performance testing |
Contributor
There was a problem hiding this comment.
remove (move below the intro)
|
|
||
| Memgraph, on the other hand, **consistently performs better** by keeping the entire dataset **in memory**, | ||
| ensuring **predictable latency and fast response times** regardless of previous operations or system state. | ||
|
|
Contributor
There was a problem hiding this comment.
Add title here, but shorter, something like "Introducing mgbench"
| framework located within our core Memgraph repository. Unlike simplistic benchmarks that run a query once and record latency, | ||
| mgbench focuses on **repeatable, controlled testing** across different conditions and vendors. | ||
|
|
||
| We designed mgbench to: |
Contributor
There was a problem hiding this comment.
Suggested change
| We designed mgbench to: | |
| <h3 className="custom-header">What sets mgbench apart?</h3> | |
Comment on lines
36
to
40
| - Eliminate noise from unrelated system activity | ||
| - Account for whether a database is **“hot” or “cold”** | ||
| - Detect how **query repetition, data freshness**, or **system-level caching** affect results | ||
| - Support **adding new vendors and workloads** easily | ||
| - Provide both **latency and throughput metrics at scale** |
Contributor
There was a problem hiding this comment.
Suggested change
| - Eliminate noise from unrelated system activity | |
| - Account for whether a database is **“hot” or “cold”** | |
| - Detect how **query repetition, data freshness**, or **system-level caching** affect results | |
| - Support **adding new vendors and workloads** easily | |
| - Provide both **latency and throughput metrics at scale** | |
| - Eliminates noise from unrelated system activity | |
| - Differentiates between **cold** and **hot** database states | |
| - Detects how **query repetition, data freshness** or **system-level caching** affect results | |
| - Supports **adding new vendors and workloads** easily | |
| - Provides both **latency and throughput metrics at scale** | |
| where you can analyze how the combination of different query types affects individual performance metrics. | ||
|
|
||
| <Callout type="info"> | ||
| Ready to test for yourself? Try out [**mgbench**](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md) with |
Contributor
There was a problem hiding this comment.
Suggested change
| Ready to test for yourself? Try out [**mgbench**](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md) with | |
| Ready to test for yourself? Try out [mgbench](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md) with | |
Comment on lines
44
to
48
| **consistent performance even under pressure**, where disk-based solutions tend to fall behind. For this reason, *mgbench* is designed | ||
| to support both [**realistic workloads**](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md#workloads), | ||
| which simulate production-like distributions of reads, writes, | ||
| and analytical queries, and [**mixed workloads**](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md#workloads), | ||
| where you can analyze how the combination of different query types affects individual performance metrics. |
Contributor
There was a problem hiding this comment.
Suggested change
| **consistent performance even under pressure**, where disk-based solutions tend to fall behind. For this reason, *mgbench* is designed | |
| to support both [**realistic workloads**](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md#workloads), | |
| which simulate production-like distributions of reads, writes, | |
| and analytical queries, and [**mixed workloads**](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md#workloads), | |
| where you can analyze how the combination of different query types affects individual performance metrics. | |
| **consistent performance even under pressure**, where disk-based solutions tend to fall behind. | |
| <h3 className="custom-header">Realistic + mixed workloads</h3> | |
| For the reasons listed above, `mgbench` supports: | |
| - [Realistic workloads](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md#workloads): Simulate production-like distributions of reads, writes, | |
| and analytical queries | |
| - [Mixed workloads](https://github.com/memgraph/memgraph/blob/master/tests/mgbench/README.md#workloads): Analyze how the combination of different query types affects individual performance metrics. | |
| spot regressions, and better understand how each database behaves under pressure. | ||
|
|
||
| <Callout type="info"> | ||
| For looking into the published bechmarks, check out [our official BenchGraph site](https://memgraph.com/benchgraph)! |
Contributor
There was a problem hiding this comment.
Suggested change
| For looking into the published bechmarks, check out [our official BenchGraph site](https://memgraph.com/benchgraph)! | |
| For looking into the published bechmarks, check out our official [BenchGraph site](https://memgraph.com/benchgraph)! | |
matea16
approved these changes
Apr 28, 2025
matea16
pushed a commit
that referenced
this pull request
Apr 28, 2025
* init * Add hardware sizing * Add vm.max_map_count explanation * Add deployment options * Add flag set suggestions * Indentation * Remove unnecessary comment * Add enterprise, queries and import sections * Finish general suggestions guide * Make under construction notes * Add todo * Update property sizes * Add backup considerations * Added overview page * Add hardware sizing * Add vm.max_map_count explanation * Add deployment options * Add flag set suggestions * Indentation * Remove unnecessary comment * Add enterprise, queries and import sections * Finish general suggestions guide * Make under construction notes * Add todo * Update property sizes * Add backup considerations * Added overview page * Main * Main * Newline * Add section for query timeout * Set up lab features * Sentence case * Remove empty construction pages * Add callout * Update GraphRAG use case * Finish memgraph in production for graphrag * Add graphrag link * Address PR comments * Evaluating memgraph (#1263) * Update initial page * Add page for evaluating memgraph -> mgbench * Add title for evaluating memgraph * Address PR comments --------- Co-authored-by: katarinasupe <supe.katarina@gmail.com> Co-authored-by: Katarina Supe <61758502+katarinasupe@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release note
Added page for Memgraph evaluation in "Memgraph in production"
Related product PRs
PRs from product repo this doc page is related to:
(paste the links to the PRs)
Checklist:
bugfixorfeaturelabel, based on the product PR type you're documenting