Difference between revisions of "M4 Caching"
From Kolmisoft Wiki
Jump to navigationJump to search
(Created page with 'The current caching system caches several HGC. When a call fails with some HGC, the IP is marked in the cache for some time, so next time the call comes from the same IP, call wi…') |
|||
| Line 1: | Line 1: | ||
The current caching system caches several HGC. When a call fails with some HGC, the IP is marked in the cache for some time, so next time the call comes from the same IP, call will be rejected with the same HGC. This removes some load from the DB and provides some protection against DDoS attacks or high bursts of CPS. | The current caching system caches several HGC. When a call fails with some HGC, the IP is marked in the cache for some time, so next time the call comes from the same IP, call will be rejected with the same HGC. | ||
This removes some load from the DB and provides some protection against DDoS attacks or high bursts of CPS. | |||
Current cached HGC with for how long cache is active (until the value is removed from the cache and call could try to pass): | Current cached HGC with for how long cache is active (until the value is removed from the cache and call could try to pass): | ||
Revision as of 15:00, 21 October 2019
The current caching system caches several HGC. When a call fails with some HGC, the IP is marked in the cache for some time, so next time the call comes from the same IP, call will be rejected with the same HGC. This removes some load from the DB and provides some protection against DDoS attacks or high bursts of CPS.
Current cached HGC with for how long cache is active (until the value is removed from the cache and call could try to pass):
- 301 - 120s
- 302 - 5s
- 303 - 10s
- 304 - 1s
- 306 - 60s
- 311 - 120s
- 313 - 10s
- 320 - 120s
