{"action":"opened","issue":{"url":"https://api.github.com/repos/concourse/concourse/issues/2776","repository_url":"https://api.github.com/repos/concourse/concourse","labels_url":"https://api.github.com/repos/concourse/concourse/issues/2776/labels{/name}","comments_url":"https://api.github.com/repos/concourse/concourse/issues/2776/comments","events_url":"https://api.github.com/repos/concourse/concourse/issues/2776/events","html_url":"https://github.com/concourse/concourse/issues/2776","id":378823835,"node_id":"MDU6SXNzdWUzNzg4MjM4MzU=","number":2776,"title":"Improve dashboard bandwidth usage","user":{"login":"william-tran","id":1084441,"node_id":"MDQ6VXNlcjEwODQ0NDE=","avatar_url":"https://avatars0.githubusercontent.com/u/1084441?v=4","gravatar_id":"","url":"https://api.github.com/users/william-tran","html_url":"https://github.com/william-tran","followers_url":"https://api.github.com/users/william-tran/followers","following_url":"https://api.github.com/users/william-tran/following{/other_user}","gists_url":"https://api.github.com/users/william-tran/gists{/gist_id}","starred_url":"https://api.github.com/users/william-tran/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/william-tran/subscriptions","organizations_url":"https://api.github.com/users/william-tran/orgs","repos_url":"https://api.github.com/users/william-tran/repos","events_url":"https://api.github.com/users/william-tran/events{/privacy}","received_events_url":"https://api.github.com/users/william-tran/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-08T16:51:14Z","updated_at":"2018-11-08T16:51:14Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"- Concourse 4.2.1 on k8s\r\n- 300 pipelines in one team\r\n- /api/v1/resources returns 3700 resources using 476 KB \r\n- /api/v1/jobs returns 1878 jobs using 2.2 MB\r\n\r\nThe size of these responses delays readiness to be able to use the search bar. \r\nThe dashboard, both HD and full, polls these every 5 seconds, which also chews through bandwidth which costs $. I've resorted to making my ingress handle these endpoints with a hardcoded `200 []` for now.\r\n\r\nTo improve this:\r\n- make search readiness depend on just the pipelines response which is small\r\n- keep the \"state of the universe\" endpoints, but create a new api for events describing both build state changes (e.g. pending to starting to finished) and pipeline config changes, so UIs can stay up to date with minimal bandwidth.\r\n "}}
{"actor":{"display_login":"william-tran"}}