{"action":"created","issue":{"url":"https://api.github.com/repos/ethereum/ethereumj/issues/430","repository_url":"https://api.github.com/repos/ethereum/ethereumj","labels_url":"https://api.github.com/repos/ethereum/ethereumj/issues/430/labels{/name}","comments_url":"https://api.github.com/repos/ethereum/ethereumj/issues/430/comments","events_url":"https://api.github.com/repos/ethereum/ethereumj/issues/430/events","html_url":"https://github.com/ethereum/ethereumj/issues/430","id":162802927,"number":430,"title":"Potential syncing bottleneck","user":{"login":"jlopp","id":288011,"avatar_url":"https://avatars.githubusercontent.com/u/288011?v=3","gravatar_id":"","url":"https://api.github.com/users/jlopp","html_url":"https://github.com/jlopp","followers_url":"https://api.github.com/users/jlopp/followers","following_url":"https://api.github.com/users/jlopp/following{/other_user}","gists_url":"https://api.github.com/users/jlopp/gists{/gist_id}","starred_url":"https://api.github.com/users/jlopp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jlopp/subscriptions","organizations_url":"https://api.github.com/users/jlopp/orgs","repos_url":"https://api.github.com/users/jlopp/repos","events_url":"https://api.github.com/users/jlopp/events{/privacy}","received_events_url":"https://api.github.com/users/jlopp/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-06-28T22:34:06Z","updated_at":"2016-06-28T22:46:59Z","closed_at":"2016-06-28T22:46:59Z","body":"This is just an informational point; not sure if you'll find it helpful. I was profiling EthereumJ 1.3.0 snapshot syncing the main network with none of our app code activated and noticed that a substantial portion of the CPU time is spent in the Transaction.getSender() function. Just an FYI - it might be low hanging fruit for a performance optimization.\r\n![screen shot 2016-06-28 at 6 31 36 pm](https://cloud.githubusercontent.com/assets/288011/16434605/e1028734-3d5e-11e6-844f-03255229547a.png)\r\n"},"comment":{"url":"https://api.github.com/repos/ethereum/ethereumj/issues/comments/229207218","html_url":"https://github.com/ethereum/ethereumj/issues/430#issuecomment-229207218","issue_url":"https://api.github.com/repos/ethereum/ethereumj/issues/430","id":229207218,"user":{"login":"Nashatyrev","id":8173857,"avatar_url":"https://avatars.githubusercontent.com/u/8173857?v=3","gravatar_id":"","url":"https://api.github.com/users/Nashatyrev","html_url":"https://github.com/Nashatyrev","followers_url":"https://api.github.com/users/Nashatyrev/followers","following_url":"https://api.github.com/users/Nashatyrev/following{/other_user}","gists_url":"https://api.github.com/users/Nashatyrev/gists{/gist_id}","starred_url":"https://api.github.com/users/Nashatyrev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Nashatyrev/subscriptions","organizations_url":"https://api.github.com/users/Nashatyrev/orgs","repos_url":"https://api.github.com/users/Nashatyrev/repos","events_url":"https://api.github.com/users/Nashatyrev/events{/privacy}","received_events_url":"https://api.github.com/users/Nashatyrev/received_events","type":"User","site_admin":false},"created_at":"2016-06-28T22:46:59Z","updated_at":"2016-06-28T22:46:59Z","body":"Yep, this is CPU hard operation, that's why it is currently executed in parallel via `ExecutorPipeline` (you see it on top the stack)\r\nBTW if you any better EC_RECOVER java implementation would be great!"}}
{"actor":{"display_login":"Nashatyrev"}}