-
- Downloads
Remove the in-memory cache (#6037)
Shields has long had an in-memory cache with some complex logic for determining when the cached values are used and when they are flushed. At the time this was implemented, squeezing cache performance was helpful since there was no downstream cache. For years now we've used Cloudflare as a CDN, so trying to cache onboard is less useful than before. Furthermore, since the cache is very small and only used in fairly restrictive ways, it probably has very little impact on performance.
Showing
- core/base-service/base-non-memory-caching.js 0 additions, 74 deletionscore/base-service/base-non-memory-caching.js
- core/base-service/index.js 0 additions, 2 deletionscore/base-service/index.js
- core/base-service/legacy-request-handler.js 4 additions, 104 deletionscore/base-service/legacy-request-handler.js
- core/base-service/legacy-request-handler.spec.js 1 addition, 62 deletionscore/base-service/legacy-request-handler.spec.js
- core/base-service/lru-cache.js 0 additions, 136 deletionscore/base-service/lru-cache.js
- core/base-service/lru-cache.spec.js 0 additions, 134 deletionscore/base-service/lru-cache.spec.js
- doc/code-walkthrough.md 5 additions, 6 deletionsdoc/code-walkthrough.md
- doc/production-hosting.md 5 additions, 7 deletionsdoc/production-hosting.md
- services/debug/debug.service.js 2 additions, 2 deletionsservices/debug/debug.service.js
- services/maintenance/maintenance.service.js 2 additions, 2 deletionsservices/maintenance/maintenance.service.js
Loading