{"action":"created","issue":{"url":"https://api.github.com/repos/WebAssembly/spec/issues/123","labels_url":"https://api.github.com/repos/WebAssembly/spec/issues/123/labels{/name}","comments_url":"https://api.github.com/repos/WebAssembly/spec/issues/123/comments","events_url":"https://api.github.com/repos/WebAssembly/spec/issues/123/events","html_url":"https://github.com/WebAssembly/spec/issues/123","id":110730542,"number":123,"title":"Significant performance regression","user":{"login":"kg","id":198130,"avatar_url":"https://avatars.githubusercontent.com/u/198130?v=3","gravatar_id":"","url":"https://api.github.com/users/kg","html_url":"https://github.com/kg","followers_url":"https://api.github.com/users/kg/followers","following_url":"https://api.github.com/users/kg/following{/other_user}","gists_url":"https://api.github.com/users/kg/gists{/gist_id}","starred_url":"https://api.github.com/users/kg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kg/subscriptions","organizations_url":"https://api.github.com/users/kg/orgs","repos_url":"https://api.github.com/users/kg/repos","events_url":"https://api.github.com/users/kg/events{/privacy}","received_events_url":"https://api.github.com/users/kg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-09T20:27:56Z","updated_at":"2015-10-09T20:47:05Z","closed_at":null,"body":"I updated to the latest revision of the spec and ml-proto is much slower than it used to be. The NBody test (https://github.com/WebAssembly/ilwasm/blob/master/third_party/tests/NBody.cs) now utilizes ~100% cpu for multiple seconds while running; it used to run at a reasonable speed.\r\n\r\nDo we care about the performance of ml-proto? Overly slow execution will hinder our ability to iterate and bias us away from real-world tests, I think."},"comment":{"url":"https://api.github.com/repos/WebAssembly/spec/issues/comments/146982332","html_url":"https://github.com/WebAssembly/spec/issues/123#issuecomment-146982332","issue_url":"https://api.github.com/repos/WebAssembly/spec/issues/123","id":146982332,"user":{"login":"lukewagner","id":9660325,"avatar_url":"https://avatars.githubusercontent.com/u/9660325?v=3","gravatar_id":"","url":"https://api.github.com/users/lukewagner","html_url":"https://github.com/lukewagner","followers_url":"https://api.github.com/users/lukewagner/followers","following_url":"https://api.github.com/users/lukewagner/following{/other_user}","gists_url":"https://api.github.com/users/lukewagner/gists{/gist_id}","starred_url":"https://api.github.com/users/lukewagner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lukewagner/subscriptions","organizations_url":"https://api.github.com/users/lukewagner/orgs","repos_url":"https://api.github.com/users/lukewagner/repos","events_url":"https://api.github.com/users/lukewagner/events{/privacy}","received_events_url":"https://api.github.com/users/lukewagner/received_events","type":"User","site_admin":false},"created_at":"2015-10-09T20:47:05Z","updated_at":"2015-10-09T20:47:05Z","body":"I think the default changed to building unopt builds (they have usable stack traces); so I'd try `make opt`.  But in general, we've collectively agreed on a few occasions that the goal of ml-proto isn't performance, it's specifying behavior cleanly.  There's a lot of O(n) operations in there that would be O(1) in a real interp."}}