Closed szelok closed 11 years ago
Yeah I've noticed that for some repos/machines/browsers it's really bad sometimes, and it's definitely on the top of my list to take care of.
Currently ungit causes the beach ball every time for me, with many identical requests pending (mac, firefox). And sometimes it goes to lost connection.
On Wed, Sep 4, 2013 at 9:23 AM, FredrikNoren notifications@github.comwrote:
Yeah I've noticed that for some repos/machines/browsers it's really bad sometimes, and it's definitely on the top of my list to take care of.
— Reply to this email directly or view it on GitHubhttps://github.com/FredrikNoren/ungit/issues/183#issuecomment-23803197 .
Having connections lost problem pretty frequently. Wonder if it's because of the update?
@nroose Yeah I've noticed that it makes too much (unnecessary) requests at times, looking into reducing them. Also think there's a bug that makes it do requests to repos you've previously browsed for some reason
@ngokchau I hope not :S If you can find something pointing towards it though it would be great
Forgot to tag but this commit should reduce memory leakage: 3b92aa55cf44c43e5db618d319063435989bc102
@FredrikNoren Seems to be working fine now. I'll keep an eye out. :)
4c48f93565a9511127443b9017c14443e0a91432 should probably help performance too (always good not to watch a ton of files :)
@szelok did your original problem of ungit taking 100% of your cpu get solved with 0.2.0?
Thing the most pressing current issues have been resolved now so closing this one
Run ungit on Windows 7. The CPU hit 100% constantly making the desktop un-usable.
Any insight of performance metrics? any suggestion of OS and h/w config?