Deploy Redis for data searching on Google Cloud C4A (Arm-based Axion VM) #26
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
| Continue scanning by reusing the cursor until it returns `0`, meaning the iteration is complete. | ||
|
|
||
| ### Measure Data Retrieval Performance | ||
| This step measures how quickly Redis can retrieve a single key from memory, helping establish a baseline for data access latency on the Arm-based VM. |
There was a problem hiding this comment.
Suggested change
| This step measures how quickly Redis can retrieve a single key from memory, helping establish a baseline for data access latency on the Arm-based VM. | |
| This step measures how quickly Redis can retrieve a single key from memory, helping to establish a baseline for data access latency on the Arm-based VM. |
|
|
||
|
|
||
| ## Redis Benchmarking by redis-benchmark | ||
| The `redis-benchmark` tool is an official performance testing utility for Redis. It helps measure throughput (requests per second) and latency (response delay) across different workloads. |
There was a problem hiding this comment.
Suggested change
| The `redis-benchmark` tool is an official performance testing utility for Redis. It helps measure throughput (requests per second) and latency (response delay) across different workloads. | |
| The `redis-benchmark` tool is an official performance testing utility for Redis. It helps to measure throughput (requests per second) and latency (response delay) across different workloads. |
| cd redis-8.2.2 | ||
| ``` | ||
| {{% notice Note %}} | ||
| Benchmarking is done on Redis 6.0.9. You can view [this Blog](https://community.arm.com/arm-community-blogs/b/infrastructure-solutions-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances) |
There was a problem hiding this comment.
This is not clear. benchmarking is done using 6.0.9 or latest?
| cd redis-8.2.2 | ||
| ``` | ||
| {{% notice Note %}} | ||
| Benchmarking is done on Redis 6.0.9. You can view [this Blog](https://community.arm.com/arm-community-blogs/b/infrastructure-solutions-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances) |
There was a problem hiding this comment.
First of all, this blog link does not work now. The blog has been assigned some other URL. Kindly verify before adding any link to the LP.
New blog link is : https://developer.arm.com/community/arm-community-blogs/b/servers-and-cloud-computing-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances.
Reframe the Note
Suggested change
| Benchmarking is done on Redis 6.0.9. You can view [this Blog](https://community.arm.com/arm-community-blogs/b/infrastructure-solutions-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances) | |
| In [this](https://developer.arm.com/community/arm-community-blogs/b/servers-and-cloud-computing-blog/posts/improve-redis-performance-by-deploying-on-alibaba-cloud-yitian-710-instances) blog, Redis version 6.0.9 is recommended for deployment on Arm-based Alibaba Yitian 710 instances, which deliver up to 36% higher throughput and 20% lower cost compared to equivalent x86-based ECS instances, making it a more efficient and cost-effective choice for Redis workloads. | |
| The [Arm Ecosystem Dashboard](https://developer.arm.com/ecosystem-dashboard/) recommends Redis version 6.0.9, the minimum recommended on the Arm platforms. |
| {{% /notice %}} | ||
|
|
||
| ### Build Redis with TLS Support | ||
| Clean any previous build artifacts (if any): |
There was a problem hiding this comment.
Suggested change
| Clean any previous build artifacts (if any): | |
| **Clean any previous build artifacts (if any):** |
| redis-server --version | ||
| redis-cli --version | ||
| ``` | ||
|
|
| ``` | ||
|
|
||
| ```output | ||
| gcpuser@lpprojectsusearm64:~> redis-server --version |
There was a problem hiding this comment.
Suggested change
| gcpuser@lpprojectsusearm64:~> redis-server --version | |
| $ redis-server --version |
| ```output | ||
| gcpuser@lpprojectsusearm64:~> redis-server --version | ||
| Redis server v=8.2.2 sha=00000000:1 malloc=jemalloc-5.3.0 bits=64 build=72ba144d8c96c783 | ||
| gcpuser@lpprojectsusearm64:~> redis-cli --version |
There was a problem hiding this comment.
Suggested change
| gcpuser@lpprojectsusearm64:~> redis-cli --version | |
| $ redis-cli --version |
…VMs) Signed-off-by: odidev <[email protected]>
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.
No description provided.