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
After some comprehensive testing, I figured out, that since Laravel 6 there are some queries that bypass Lada Cache. This doesn't cause unexpected behavior but reduces the effect of the cache. If used with Debug Bar, the "Queries" tab must not show any queries after the second page load. All queries which are still shown bypass the cache.
The text was updated successfully, but these errors were encountered:
@spiritix How do we know it's not the debug bar that's having the error? If I remember correctly I noticed activity on redis monitor cli while the debug bar didn't seem to change behaviour, but I'll take a look at this again to verify.
@xwiz First, this seems to be edge case that only occurs with very complex and rare queries. It's not like a large portion of the queries would bypass the cache. But then to your question - indeed, we'd need to verify that this is not a Debug Bar issue. Theoretically, a query that is being handled by Lada Cache is obviously not executed against the database backend but instead routed via the cache. So the Debug Bar should not be able to even access it.
After some comprehensive testing, I figured out, that since Laravel 6 there are some queries that bypass Lada Cache. This doesn't cause unexpected behavior but reduces the effect of the cache. If used with Debug Bar, the "Queries" tab must not show any queries after the second page load. All queries which are still shown bypass the cache.
The text was updated successfully, but these errors were encountered: