# GRV cache option and stale reads

**URL:** <https://forums.foundationdb.org/t/grv-cache-option-and-stale-reads/4271>\
**Category:** Using FoundationDB\
**Tags:** performance\
**Created:** [November 30, 2023, 12:01pm UTC](https://forums.foundationdb.org/t/grv-cache-option-and-stale-reads/4271 "2023-11-30T12:01:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mping-exo](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/mping-exo/32/1374_2.png) [@mping-exo](https://forums.foundationdb.org/u/mping-exo)\
**Post date:** [November 30, 2023, 12:01pm UTC](https://forums.foundationdb.org/t/grv-cache-option-and-stale-reads/4271/1 "2023-11-30T12:01:34Z")

</div>

How does the `setUseGrvCache` flag affects performance? Can it allow for stale reads to happen under slightly loaded cluster?

I have the impression that with this cache, the grv is cached at the (native) client level, so any commits that may happen during a read tx may result in a stale read, but I didn’t manage to exhibit this behaviour.  
Also, for this case of stale reads on a readonly transaction, I guess the tx can be safely retried (either hoping for the grv cache to update, or retried with grv cache skip to force a refresh)?

Thanks
