{"action":"closed","issue":{"url":"https://api.github.com/repos/DataBrewery/cubes/issues/446","repository_url":"https://api.github.com/repos/DataBrewery/cubes","labels_url":"https://api.github.com/repos/DataBrewery/cubes/issues/446/labels{/name}","comments_url":"https://api.github.com/repos/DataBrewery/cubes/issues/446/comments","events_url":"https://api.github.com/repos/DataBrewery/cubes/issues/446/events","html_url":"https://github.com/DataBrewery/cubes/issues/446","id":249682506,"node_id":"MDU6SXNzdWUyNDk2ODI1MDY=","number":446,"title":"Cube queries not using cache on mariadb","user":{"login":"schwab","id":1517342,"node_id":"MDQ6VXNlcjE1MTczNDI=","avatar_url":"https://avatars2.githubusercontent.com/u/1517342?v=4","gravatar_id":"","url":"https://api.github.com/users/schwab","html_url":"https://github.com/schwab","followers_url":"https://api.github.com/users/schwab/followers","following_url":"https://api.github.com/users/schwab/following{/other_user}","gists_url":"https://api.github.com/users/schwab/gists{/gist_id}","starred_url":"https://api.github.com/users/schwab/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/schwab/subscriptions","organizations_url":"https://api.github.com/users/schwab/orgs","repos_url":"https://api.github.com/users/schwab/repos","events_url":"https://api.github.com/users/schwab/events{/privacy}","received_events_url":"https://api.github.com/users/schwab/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-08-11T16:15:41Z","updated_at":"2018-07-05T12:49:49Z","closed_at":"2018-07-05T12:49:49Z","author_association":"NONE","body":"Mariadb has a query cache mechanism which caches sql queries when it sees that the request is identical to recent queries. This results in a huge performance boost for subsequent queries. The mechanism for enabling this and some things which cause it not be used are described  @ https://mariadb.com/kb/en/mariadb/query-cache.  \r\n\r\nI have notice however, that python cube generated (for instance a simple /members lookup) always takes ~3.4  to run.  However, if I run the same query directly against the mariadb server using the terminal client, it comes back in ~3.4sec the first time, but subsequent requests take <1ms.  Why then is python cubes query not resulting in a cached hit on mariadb when the same request is sent  multiple times (in order with no writes going on) when it's sent by python cubes?  \r\n\r\nIs there anything I can do to further troubleshoot this problem or configure slicer to allow it to get mariadb's cached version of the query?\r\n"}}
{"actor":{"display_login":"schwab"}}