{"action":"created","issue":{"url":"https://api.github.com/repos/bikeath1337/EvaporateJS/issues/4","repository_url":"https://api.github.com/repos/bikeath1337/EvaporateJS","labels_url":"https://api.github.com/repos/bikeath1337/EvaporateJS/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/bikeath1337/EvaporateJS/issues/4/comments","events_url":"https://api.github.com/repos/bikeath1337/EvaporateJS/issues/4/events","html_url":"https://github.com/bikeath1337/EvaporateJS/pull/4","id":194850312,"number":4,"title":"POC Enhances Evaporate to Support Node File Streams (Readable)","user":{"login":"bikeath1337","id":243237,"avatar_url":"https://avatars.githubusercontent.com/u/243237?v=3","gravatar_id":"","url":"https://api.github.com/users/bikeath1337","html_url":"https://github.com/bikeath1337","followers_url":"https://api.github.com/users/bikeath1337/followers","following_url":"https://api.github.com/users/bikeath1337/following{/other_user}","gists_url":"https://api.github.com/users/bikeath1337/gists{/gist_id}","starred_url":"https://api.github.com/users/bikeath1337/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bikeath1337/subscriptions","organizations_url":"https://api.github.com/users/bikeath1337/orgs","repos_url":"https://api.github.com/users/bikeath1337/repos","events_url":"https://api.github.com/users/bikeath1337/events{/privacy}","received_events_url":"https://api.github.com/users/bikeath1337/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-12-11T19:23:37Z","updated_at":"2016-12-13T20:57:06Z","closed_at":"2016-12-12T13:40:16Z","pull_request":{"url":"https://api.github.com/repos/bikeath1337/EvaporateJS/pulls/4","html_url":"https://github.com/bikeath1337/EvaporateJS/pull/4","diff_url":"https://github.com/bikeath1337/EvaporateJS/pull/4.diff","patch_url":"https://github.com/bikeath1337/EvaporateJS/pull/4.patch"},"body":"Tries to demonstrate how it works by harnessing Electron."},"comment":{"url":"https://api.github.com/repos/bikeath1337/EvaporateJS/issues/comments/266859572","html_url":"https://github.com/bikeath1337/EvaporateJS/pull/4#issuecomment-266859572","issue_url":"https://api.github.com/repos/bikeath1337/EvaporateJS/issues/4","id":266859572,"user":{"login":"bikeath1337","id":243237,"avatar_url":"https://avatars.githubusercontent.com/u/243237?v=3","gravatar_id":"","url":"https://api.github.com/users/bikeath1337","html_url":"https://github.com/bikeath1337","followers_url":"https://api.github.com/users/bikeath1337/followers","following_url":"https://api.github.com/users/bikeath1337/following{/other_user}","gists_url":"https://api.github.com/users/bikeath1337/gists{/gist_id}","starred_url":"https://api.github.com/users/bikeath1337/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bikeath1337/subscriptions","organizations_url":"https://api.github.com/users/bikeath1337/orgs","repos_url":"https://api.github.com/users/bikeath1337/repos","events_url":"https://api.github.com/users/bikeath1337/events{/privacy}","received_events_url":"https://api.github.com/users/bikeath1337/received_events","type":"User","site_admin":false},"created_at":"2016-12-13T20:57:06Z","updated_at":"2016-12-13T20:57:06Z","body":"Excellent. I did tests this morning and have a simplification that I will merge; however, I inspected the heap and saw no copies of allocated memory related to uploading parts.\r\n\r\nINTERSTINGLY (and fortunately), I did observer that Chrome and Electron Chromium become CPU intensive when a \"large\" part gets sent to the browser to handle `xhr.send(payload)`.  For example, with a part size of 50MB, the CPU maxes out and takes about 7 elapsed seconds for each part. The cost of calculating the checksum was insignificant, so I have no idea what is happening in Chrome at the point, but whatever it does does not seem to reflect in memory use in a heap report.\r\n\r\nI also found that Chromium did not report the XHR puts in the developer XHR list if the part size was more than 50 MB. In Electron, Chromium completely went away for a part size of 100MB. No errors reported but I assume it was memory-related.\r\n\r\nOne more plus 1 for smaller part sizes!"}}
{"actor":{"display_login":"bikeath1337"}}