You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, profiled search requests can use the cache, which can lead to very different profiling times if the same query is profiled twice or you can have a slow took time but a fast profile result . Profiling should never really use the cache at all because of the nature of profiling.
Related with #29024 although what is here proposed is that the profile works as if the query was never cached. Therefore it can lead to fast took time but slow profile results.
The text was updated successfully, but these errors were encountered:
This change disables the query and request cache when
profile is set to true in the request. This means that profiled queries
will not check caches to execute the query and the result will never be
added in the cache either.
Closeselastic#33298
This change disables the query and request cache when
profile is set to true in the request. This means that profiled queries
will not check caches to execute the query and the result will never be
added in the cache either.
Closes#33298
This change disables the query and request cache when
profile is set to true in the request. This means that profiled queries
will not check caches to execute the query and the result will never be
added in the cache either.
Closes#33298
Today, profiled search requests can use the cache, which can lead to very different profiling times if the same query is profiled twice or you can have a slow
took
time but a fast profile result . Profiling should never really use the cache at all because of the nature of profiling.Related with #29024 although what is here proposed is that the profile works as if the query was never cached. Therefore it can lead to fast
took
time but slow profile results.The text was updated successfully, but these errors were encountered: