Issue to problems related to KP caching system #2587
Description
This is a replacement for issue #2374
I have deployed the KP result caching system to all endpoints on arax.ncats.io /, /test, /beta, /devED, /devLM, /shepherd, as well as it is live on arax.ci.transltr.io. It appears to be working mostly as designed. One minor bug has been noted and will be fixed, but should not impact most operation. If you notice a problem, please let me know, ideally on this issue.
Random points:
- When remaining Python 3.9 endpoints are upgraded to Python 3.12, the cache MAY fail if Python 3.12 pickling is not compatible with 3.9 pickling. We would need to clear the cache.
- The cache currently IS persistent across restarts of the service.
- Each individual endpoint has its own private cache, cache is not shared across endpoints.
- All HTTPS requests to KPs are cached by the system
- Pathfinder is also cached by the system
- xDTD and xCRG are NOT cached by the system at this time. I tried and results that emerge from the cache cause downstream failures for reasons that I cannot solve at the moment.
- There is an option in the lower left part of the ARAX GUI to peer into the cache
Let me know how it goes