Cache period?
When I first hit my API it checks against an array in Firestore, and takes ~2s to respond. Subsequent calls are much faster, which implies that the node is caching the array it pulls, but only for a few minutes.
Is there some way I can extend this caching to 24h, as the data it pulls is not updated often?
Solution:Jump to solution
@JamesG are you in free or starter plans? They have a cold start meaning first request after a while will take little bit longer for service to be warmed up. After that subsequent requests will be faster in that session.
5 Replies
AI Support Bot Information
<@791353343426953246> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
It seems that there isn't specific guidance in the BuildShip documentation regarding extending caching duration for Firestore data. However, you might still be able to achieve similar functionality by using a combination of nodes and maintaining state within your workflow or using your own caching mechanism.
If you have more detailed questions or need more specific guidance, it might be best to reach out via in-app support for more tailored assistance.
BuildShip AI Support
Solution
@JamesG are you in free or starter plans? They have a cold start meaning first request after a while will take little bit longer for service to be warmed up. After that subsequent requests will be faster in that session.
You can upgrade if you do not want the cold start ie every request to be fast with service always being warm.
Ah that's great. I have a free account for messing around and a paid account for a project, so I guess that means I should assume that the >1st return times will always apply when I replicate this in production. Thanks @Harini!