{"action":"closed","issue":{"url":"https://api.github.com/repos/dhasenan/pierce/issues/4","repository_url":"https://api.github.com/repos/dhasenan/pierce","labels_url":"https://api.github.com/repos/dhasenan/pierce/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/dhasenan/pierce/issues/4/comments","events_url":"https://api.github.com/repos/dhasenan/pierce/issues/4/events","html_url":"https://github.com/dhasenan/pierce/issues/4","id":170298175,"number":4,"title":"Clear out read articles","user":{"login":"dhasenan","id":578393,"avatar_url":"https://avatars.githubusercontent.com/u/578393?v=3","gravatar_id":"","url":"https://api.github.com/users/dhasenan","html_url":"https://github.com/dhasenan","followers_url":"https://api.github.com/users/dhasenan/followers","following_url":"https://api.github.com/users/dhasenan/following{/other_user}","gists_url":"https://api.github.com/users/dhasenan/gists{/gist_id}","starred_url":"https://api.github.com/users/dhasenan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dhasenan/subscriptions","organizations_url":"https://api.github.com/users/dhasenan/orgs","repos_url":"https://api.github.com/users/dhasenan/repos","events_url":"https://api.github.com/users/dhasenan/events{/privacy}","received_events_url":"https://api.github.com/users/dhasenan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-09T23:53:00Z","updated_at":"2016-08-09T23:55:52Z","closed_at":"2016-08-09T23:55:52Z","body":"Document sizes for Subscription are getting pretty big -- like I've been subscribed to a person who posts 150 times per day and I've been watching them for bloody ages, so my subscriptions are huge. /Users/Get downloads 2.3MB! And it takes over two seconds. I've got about 60,000 read article records in my user.\r\n\r\nThis is especially noticeable because we save User and Subscription in the same document.\r\n\r\nI can trim it to 200 entries each, trivially. I had an idea a while ago to remove stuff that was older than a certain date, which would let me cut it to 100 entries; however, that relied on storing a tuple of two or more values instead of a string, so it's not going to save me any appreciable amount of bandwidth etc.\r\n\r\nIn my case, this will save me about 70% of the size, which should get me loading the page 1.6 seconds faster."}}
{"actor":{"display_login":"dhasenan"}}