{"action":"opened","issue":{"url":"https://api.github.com/repos/spiermar/d3-flame-graph/issues/108","repository_url":"https://api.github.com/repos/spiermar/d3-flame-graph","labels_url":"https://api.github.com/repos/spiermar/d3-flame-graph/issues/108/labels{/name}","comments_url":"https://api.github.com/repos/spiermar/d3-flame-graph/issues/108/comments","events_url":"https://api.github.com/repos/spiermar/d3-flame-graph/issues/108/events","html_url":"https://github.com/spiermar/d3-flame-graph/issues/108","id":361960923,"node_id":"MDU6SXNzdWUzNjE5NjA5MjM=","number":108,"title":"Poor performance on large data sets","user":{"login":"wonder-mice","id":1161846,"node_id":"MDQ6VXNlcjExNjE4NDY=","avatar_url":"https://avatars0.githubusercontent.com/u/1161846?v=4","gravatar_id":"","url":"https://api.github.com/users/wonder-mice","html_url":"https://github.com/wonder-mice","followers_url":"https://api.github.com/users/wonder-mice/followers","following_url":"https://api.github.com/users/wonder-mice/following{/other_user}","gists_url":"https://api.github.com/users/wonder-mice/gists{/gist_id}","starred_url":"https://api.github.com/users/wonder-mice/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wonder-mice/subscriptions","organizations_url":"https://api.github.com/users/wonder-mice/orgs","repos_url":"https://api.github.com/users/wonder-mice/repos","events_url":"https://api.github.com/users/wonder-mice/events{/privacy}","received_events_url":"https://api.github.com/users/wonder-mice/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-19T23:11:18Z","updated_at":"2018-09-19T23:11:18Z","closed_at":null,"author_association":"NONE","body":"With large data sets (more than 100000 nodes, depth around 300) performance is very poor. Even on relatively fast machine it's close to unusable. My naive assumption is that flame graph creates all d3 nodes up front and browser just can't render that much responsively.\r\n\r\nIt would be nice to optimize this. E.g. when node width is less than 1px (or some other value), render a placeholder box that represents this node and all its children. Or any other technique, it was just an example.\r\n\r\nThe reason I'm switching from svg based original flamegraph implementation (other than Perl, obscure data format and bunch of untrackable bugs) is that it is very slow on large data sets. Would be nice to see d3-flame-graph handling large data sets better. There is also https://github.com/jlfwong/speedscope, that seems to feature large data sets support, but it's much more involved for my purposes."}}
{"actor":{"display_login":"wonder-mice"}}