{"action":"created","issue":{"url":"https://api.github.com/repos/owncloud/core/issues/26909","repository_url":"https://api.github.com/repos/owncloud/core","labels_url":"https://api.github.com/repos/owncloud/core/issues/26909/labels{/name}","comments_url":"https://api.github.com/repos/owncloud/core/issues/26909/comments","events_url":"https://api.github.com/repos/owncloud/core/issues/26909/events","html_url":"https://github.com/owncloud/core/issues/26909","id":199565178,"number":26909,"title":"Separate DB connections for read and write","user":{"login":"schnidrig","id":8652424,"avatar_url":"https://avatars.githubusercontent.com/u/8652424?v=3","gravatar_id":"","url":"https://api.github.com/users/schnidrig","html_url":"https://github.com/schnidrig","followers_url":"https://api.github.com/users/schnidrig/followers","following_url":"https://api.github.com/users/schnidrig/following{/other_user}","gists_url":"https://api.github.com/users/schnidrig/gists{/gist_id}","starred_url":"https://api.github.com/users/schnidrig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/schnidrig/subscriptions","organizations_url":"https://api.github.com/users/schnidrig/orgs","repos_url":"https://api.github.com/users/schnidrig/repos","events_url":"https://api.github.com/users/schnidrig/events{/privacy}","received_events_url":"https://api.github.com/users/schnidrig/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-01-09T14:29:35Z","updated_at":"2017-01-10T18:09:57Z","closed_at":null,"body":"**Database:**\r\n\r\nMariadb Galera cluster.\r\nMaxscale: read/write spliter\r\n\r\n**ownCloud version:**\r\n\r\n8.1\r\n\r\n### Description\r\n\r\nWe at SWITCH and also some other NRENs noticed, that when using a galera \r\ncluster, one also has to use an sql-proxy doing a read / write split.\r\nOtherwise the db performance gets very, very bad due to some locking problems.\r\n\r\nAt SWITCH we use maxscale 1.3 for this. Unfortunately maxscale with \r\nthe read/write splitter is a terrible CPU hog. \r\n\r\nBut why should we operator have to retrofit OC with that feature? \r\nWouldn't it be much more efficient, if the code did use two connections. \r\nOne for write and a second one for read only db queries?\r\n\r\nThen we could simply load balance the reads without having to inspect them.\r\nThis would save a awful lot of CPU cycles and as side effect also make OC a bit greener ;-)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/owncloud/core/issues/comments/271651944","html_url":"https://github.com/owncloud/core/issues/26909#issuecomment-271651944","issue_url":"https://api.github.com/repos/owncloud/core/issues/26909","id":271651944,"user":{"login":"PVince81","id":277525,"avatar_url":"https://avatars.githubusercontent.com/u/277525?v=3","gravatar_id":"","url":"https://api.github.com/users/PVince81","html_url":"https://github.com/PVince81","followers_url":"https://api.github.com/users/PVince81/followers","following_url":"https://api.github.com/users/PVince81/following{/other_user}","gists_url":"https://api.github.com/users/PVince81/gists{/gist_id}","starred_url":"https://api.github.com/users/PVince81/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PVince81/subscriptions","organizations_url":"https://api.github.com/users/PVince81/orgs","repos_url":"https://api.github.com/users/PVince81/repos","events_url":"https://api.github.com/users/PVince81/events{/privacy}","received_events_url":"https://api.github.com/users/PVince81/received_events","type":"User","site_admin":false},"created_at":"2017-01-10T18:09:57Z","updated_at":"2017-01-10T18:09:57Z","body":"Are there other software using the same approach ? (just out of curiosity)\r\n\r\n@DeepDiver1975 @butonic @PhilippSchaffrath "}}
{"actor":{"display_login":"PVince81"}}