Changes between Initial Version and Version 1 of Ticket #35651
- Timestamp:
- Aug 1, 2024, 5:12:48 AM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35651
- Property Summary django redis cache not really using connection pooling → The number of Redis connections has been continuously increasing.
-
Ticket #35651 – Description
initial v1 3 3 After debugging, I found that whenever the cache method is called, the `RedisCacheClient `class is reinitialized, and in the `__init__` function of `RedisCacheClient`, the connection pool is set to empty. 4 4 5 This causes the `_get_connection_pool` method of `RedisCacheClient` to always create a new connection pool instead of using the existing one.5 This causes the `_get_connection_pool` method of `RedisCacheClient` to always create a new connection pool and a new connection instead of using the existing one. 6 6 7 7 {{{