{"action":"created","issue":{"url":"https://api.github.com/repos/idno/Known/issues/972","labels_url":"https://api.github.com/repos/idno/Known/issues/972/labels{/name}","comments_url":"https://api.github.com/repos/idno/Known/issues/972/comments","events_url":"https://api.github.com/repos/idno/Known/issues/972/events","html_url":"https://github.com/idno/Known/issues/972","id":95647875,"number":972,"title":"Database size","user":{"login":"metaltoast","id":13380763,"avatar_url":"https://avatars.githubusercontent.com/u/13380763?v=3","gravatar_id":"","url":"https://api.github.com/users/metaltoast","html_url":"https://github.com/metaltoast","followers_url":"https://api.github.com/users/metaltoast/followers","following_url":"https://api.github.com/users/metaltoast/following{/other_user}","gists_url":"https://api.github.com/users/metaltoast/gists{/gist_id}","starred_url":"https://api.github.com/users/metaltoast/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/metaltoast/subscriptions","organizations_url":"https://api.github.com/users/metaltoast/orgs","repos_url":"https://api.github.com/users/metaltoast/repos","events_url":"https://api.github.com/users/metaltoast/events{/privacy}","received_events_url":"https://api.github.com/users/metaltoast/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-17T12:31:00Z","updated_at":"2015-07-18T10:33:15Z","closed_at":null,"body":"I'm running a small Known instance with 11 users and about 80 posts as it stands (there's no custom post types but about 50 posts are images). The database is already 8.2MB. This is unsustainable as once over 2 or 3 thousand entities the database will be into the hundreds of MB.\r\n\r\nMy WordPress installation by comparison with 70 posts (and one user, plus metadata) is 1.0MB.\r\n\r\nThis appears largely down to Known's use of long ID strings and repetition (posting an entity and then a second entity (with associated metadata) saying \"*user* posted...\" being created.\r\n\r\nAre there any plans to look at this and put the more standard elements of an entity (ie. visibility, date created/ modified, user, slug, title, content etc) into one record and the associated metadata into a second table - similar to WordPress. Along with reducing the size of UIDs it will make Known much more sysadmin friendly."},"comment":{"url":"https://api.github.com/repos/idno/Known/issues/comments/122527960","html_url":"https://github.com/idno/Known/issues/972#issuecomment-122527960","issue_url":"https://api.github.com/repos/idno/Known/issues/972","id":122527960,"user":{"login":"mapkyca","id":124070,"avatar_url":"https://avatars.githubusercontent.com/u/124070?v=3","gravatar_id":"","url":"https://api.github.com/users/mapkyca","html_url":"https://github.com/mapkyca","followers_url":"https://api.github.com/users/mapkyca/followers","following_url":"https://api.github.com/users/mapkyca/following{/other_user}","gists_url":"https://api.github.com/users/mapkyca/gists{/gist_id}","starred_url":"https://api.github.com/users/mapkyca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mapkyca/subscriptions","organizations_url":"https://api.github.com/users/mapkyca/orgs","repos_url":"https://api.github.com/users/mapkyca/repos","events_url":"https://api.github.com/users/mapkyca/events{/privacy}","received_events_url":"https://api.github.com/users/mapkyca/received_events","type":"User","site_admin":false},"created_at":"2015-07-18T10:33:15Z","updated_at":"2015-07-18T10:33:15Z","body":"<a href=\"\" class=\"u-in-reply-to\"></a><a href=\"https://github.com/idno/Known/issues/972\" class=\"u-in-reply-to\"></a>Chiming in as well: \r\n\r\nThe current schema approach is very easy to build for, which trumps scaling issues for the majority of users, of course everyone's usecase is different. \r\n\r\nThat said, the mysql schema could probably do with some optimisation.\r\n\r\nNot entirely unrelated, this kind of object based approach maps pretty well onto systems like cassandra, which works pretty well on large high use sites."}}