You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/develop/interact/search-and-query/best-practices/dev-to-prod-best-practices.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
Title: Moving from Development to Production with Redis Query Engine
2
+
Title: Move from Development to Production with Redis Query Engine
3
3
alwaysopen: false
4
4
categories:
5
5
- docs
@@ -72,11 +72,11 @@ RQE offers several configurable parameters that influence query results and perf
72
72
- Minimize latency during testing by locating test clients in the same network as the Redis instance.
73
73
- For Redis Cloud, ensure test machines are in a **VPC-peered environment** with the target Redis database.
74
74
75
-
## Sizing Requirements
75
+
## Sizing requirements
76
76
77
77
Redis Search has resource requirements distinct from general caching use cases. Proper sizing ensures that the system can handle production workloads efficiently.
78
78
79
-
### Key Considerations:
79
+
### Key considerations:
80
80
1. CPU:
81
81
- Adequate CPU resources are critical<!--, especially when using QPF-->.
82
82
- Ensure CPUs are not over-subscribed with search threads and shard processes.
@@ -88,7 +88,7 @@ Redis Search has resource requirements distinct from general caching use cases.
88
88
### Tools:
89
89
- Use the [Redis Search Sizing Calculator](https://redis.io/redisearch-sizing-calculator/) to estimate resource requirements based on your dataset and workload.
90
90
91
-
## Demand Spikes
91
+
## Demand spikes
92
92
93
93
Production environments must be sized for peak load scenarios to ensure performance remains acceptable under maximum stress.
0 commit comments