whats the maximum allowed ExpiryTimeInSecs for KVM caching operations?

[bbhatia]

whats the maximum allowed ExpiryTimeInSecs for KVM caching operations?

[dchiesa1]

I don't know. Why do you care?

What are you trying to accomplish?

[bbhatia]

I wanted to keep credentials which i know will never change so wanted to keep it in cache for long time so was curious how long i can keep it?

[#4]

Up to my knowledge KVM changes through policy take upto 2 minutes to reflect.

[#5]

@Bharat please go through below link, I hope you will get your answer.

https://community.apigee.com/questions/35887/how-to-refresh-the-kvm-cache-forcefully.html

[dchiesa1]

For your use case, the maximum cache lifetime doesn't matter, does it?

If you use the KVM to store information that "never changes", and if you use the KVM GET policy to retrieve that information at runtime, you will always be assured that the proxy will get the correct data.

SOMETIMES the KVM GET will read from the cache. This will take less than 1ms. Sometimes the KVM will read from persistent store, which will take about ~1ms. But it doesn't really matter, practically speaking. It will make no difference to your API proxy. And the difference in time will be undetectable for practical purposes.

If I were you I'd set the cache TTL to be 600 seconds and be done with it.