$ 50.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 1182 |
| Technical Name |
redis_ultimate |
| License | OPL-1 |
| Website | http://nguyentuann1004@gmail.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 1182 |
| Technical Name |
redis_ultimate |
| License | OPL-1 |
| Website | http://nguyentuann1004@gmail.com |
| Versions | 17.0 18.0 19.0 |
Redis Ultimate
One module. Three superpowers. Zero downtime. Replace filesystem sessions with Redis, share @ormcache across all workers with hybrid L1/L2 caching, and manage everything from a beautiful admin dashboard inside Odoo Settings.
The Challenge
Scaling Odoo with multiple workers behind a load balancer? Filesystem sessions force sticky sessions, and each worker keeps its own in-memory ORM cache — causing cold-cache penalties after every restart. Most Redis modules only solve one of these problems. Redis Ultimate solves both, with a dashboard to monitor and manage everything.
|
🔐
Redis Session StoreStore HTTP sessions in Redis with automatic TTL. Enable load-balancing across multiple Odoo workers without sticky sessions. Transparent migration from filesystem. |
⚡
Hybrid L1/L2 ORM CacheL1 in-process cache for speed + L2 Redis for sharing across workers. All @ormcache namespaces supported: default, assets, templates, routing, groups. |
📊
Admin DashboardReal-time monitoring: memory usage, total keys, hit/miss ratio, server version, uptime, and active clients — all from Odoo Settings. |
|
🛡️
Graceful FallbackIf Redis becomes unreachable, Odoo automatically falls back to filesystem sessions and in-memory LRU cache. Your business keeps running — no crashes, no downtime. |
🔌
One-Click ActionsTest connection with latency measurement, flush all sessions (log out users), or flush ORM cache — all with confirmation dialogs from the Settings UI. |
⚙️
Flexible ConfigurationConfigure via odoo.conf (highest priority) or Settings UI. Supports SSL, custom database index, key prefix for shared Redis, and per-feature TTL. |
Feature Spotlight: Hybrid L1/L2 ORM Cache
Competitor modules that only use Redis for ORM cache add network latency to every cache read. Redis Ultimate uses a smarter architecture:
L1 (In-Process) — Ultra-fast local LRU cache in Python memory for sub-microsecond reads. L2 (Redis Shared) — Centralized cache so all workers share the same entries. On cache miss in L1, check L2. On L2 hit, populate L1. Result: maximum speed and maximum sharing. No cold-cache penalty after worker restarts!
How It Works
Three steps to production-ready Redis integration.
Install & Configure
Install the module and run pip install redis. Configure your Redis server
via odoo.conf or the Settings UI. Click Test Connection to verify.
Enable Sessions & ORM Cache
Toggle Redis Sessions and Redis ORM Cache. Set TTL values for session expiration and cache lifetime. Restart Odoo to activate the new backends.
Monitor & Manage
Use the built-in dashboard to monitor memory, keys, and hit ratio in real time. Flush sessions or cache when needed — all from Odoo Settings.
See It In Action
Real screenshots from Odoo Settings showing connection setup, live dashboard, and cache management.
Redis Server Connection
Configure host, port, password, database index, SSL, and key prefix. One-click Test Connection with real-time status badge (Connected / Disconnected / Error).
Real-Time Admin Dashboard
Monitor memory usage, total keys, hit/miss ratio with progress bar, server version, uptime, active clients, key prefix, and SSL status — all in one view.
Redis Session Store
Enable Redis sessions with configurable TTL (default: 7 days). Flush All Sessions button to instantly log out all users when needed.
Hybrid ORM Cache
Enable shared L2 Redis cache for @ormcache with configurable TTL (default: 1 day). Flush ORM Cache to clear stale cached data across all workers.
Configuration & Graceful Fallback
Clear documentation built into Settings: odoo.conf takes priority over UI settings, server restart required for backend changes, and automatic fallback if Redis goes down.
Redis Ultimate vs Competitors
| Feature | Redis Ultimate | Sessions Only | ORM Cache Only |
|---|---|---|---|
| Redis Session Store | ✓ | ✓ | ✗ |
| Redis ORM Cache | ✓ | ✗ | ✓ |
| Hybrid L1/L2 Cache | ✓ | ✗ | ✗ |
| Admin Dashboard | ✓ | ✗ | ✗ |
| Graceful Fallback | ✓ | ✗ | ✗ |
| Sessions + ORM Cache in one module | ✓ | ✗ | ✗ |
Quick Configuration
Add to your odoo.conf (recommended for production):
[options] redis_host = 127.0.0.1 redis_port = 6379 redis_password = redis_db = 1 redis_ssl = false redis_key_prefix = odoo redis_session_enabled = true redis_ormcache_enabled = true redis_session_ttl = 604800 redis_ormcache_ttl = 86400
Requires: pip install redis — Compatible with Redis 5.x, 6.x, 7.x+
Frequently Asked Questions
| Do I need sticky sessions with this module? No. When Redis Sessions is enabled, all HTTP sessions are stored in Redis. Any Odoo worker can serve any request — perfect for load-balanced deployments behind nginx, HAProxy, or cloud load balancers. |
| What happens if Redis goes down? Odoo automatically falls back to filesystem sessions and in-memory ORM cache. No crashes, no downtime. When Redis comes back, the module reconnects automatically. |
odoo.conf or Settings UI — which takes priority?
odoo.conf parameters always take highest priority.
Settings UI values are used as fallback when odoo.conf values are not set.
Changes require an Odoo server restart to take effect.
|
Can I share one Redis instance with multiple Odoo databases?
Yes. Use different redis_db indexes (0–15) or different
redis_key_prefix values per Odoo instance to isolate keys safely.
|
Need Help?
Full support included. Questions, customization requests, or issues — just reach out!
nguyentuann1004@gmail.comVersion: 17.0.1.0.0 | License: OPL-1 | Author: Tuan Nguyen Van
Compatible with Odoo 17 Community, Enterprise, and Odoo.sh
© 2026 Tuan Nguyen Van. All rights reserved.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module