Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Twitter Has Become Browser Poison

mikecanex.wordpress.com

Post reply on HN
Print view View original

21–30 of 108 posts

Re: New Twitter Has Become Browser Poison

#21

Post by russ »

Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the number of polls and their frequencies. Timeline refreshes are dropped back to 90 seconds when the tab isn't focused, but not sure about other ones.

As most people have reported, infinite scroll is an easy way to introduce a slowdown over time. The sheer number of DOM nodes becomes quite significant - there are things we can do to ameliorate that issue, as well. Will take a look tomorrow. The feedback is greatly appreciated.

Re: New Twitter Has Become Browser Poison

#23

Post by seldo »

ComputerGuru wrote: post #13
epi0Bauqu wrote: post #10

I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas after a day it is consuming about half a gig of memory, forcing me to kill and restart.

Firefox has crazy memory leaks. Don't blame it on twitter, regardless how bad their code may be. A tab should be completely and utterly destroyed when refreshed. It doesn't matter how much memory it used, refreshing it or navigating away from that page should (ignoring optimizations, caching, etc. etc. etc.) be like you were never there. Just look at the hundreds of complaints here: http://neosmart.net/blog/2008/fire…

I have been using it in Chrome and new Twitter has been unreasonably slow. A friend who works at Twitter has acknowledged that they know about the issue and are working on it.

Re: New Twitter Has Become Browser Poison

#24

Post by epi0Bauqu »

ComputerGuru wrote: post #13
epi0Bauqu wrote: post #10

I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas after a day it is consuming about half a gig of memory, forcing me to kill and restart.

Firefox has crazy memory leaks. Don't blame it on twitter, regardless how bad their code may be. A tab should be completely and utterly destroyed when refreshed. It doesn't matter how much memory it used, refreshing it or navigating away from that page should (ignoring optimizations, caching, etc. etc. etc.) be like you were never there. Just look at the hundreds of complaints here: http://neosmart.net/blog/2008/fire…

That may be the case, but I've left other sites open all day and they don't accumulate 500MB of memory.

Re: New Twitter Has Become Browser Poison

#25

Post by kragen »

russ wrote: post #21

Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the number of polls and their frequencies. Timeline refreshes are dropped back to 90 seconds when the tab isn't focused, but not sure about other ones. As most people have reported, inf…

It also doesn't work in the version of Arora I have. I imagine it will suck as much as Facebook does on the Kindle browser. Is there a version of Twitter that will work in a plain HTML browser with cookies and no JS? Please?

Re: New Twitter Has Become Browser Poison

#27

Post by russ »

kragen wrote: post #25
russ wrote: post #21

Over time, NewTwitter does incur a large memory footprint. I've been traveling for a month and haven't looked into the problem in depth, but I'd bet the major culprit is our aggressive caching techniques. It's also worth investigating the number of polls and their frequencies. Timeline refreshes are dropped back to 90 seconds when the tab isn't focused, but not sure about other ones. As most people have reported, inf…

It also doesn't work in the version of Arora I have. I imagine it will suck as much as Facebook does on the Kindle browser. Is there a version of Twitter that will work in a plain HTML browser with cookies and no JS? Please?

Try http://mobile.twitter.com

Re: New Twitter Has Become Browser Poison

#28

Post by kragen »

CrazedGeek wrote: post #4
watmough wrote: post #3

Agreed, the new twitter is way demanding compared to the older version. Once they stop allowing the old version, I'll probably have twitter loaded much less. On a core 2 duo, even scrolling in new twitter is way below par. Is there a low cpu-usage client? I tried one of the flash based ones, but it brought the fans permanently on on my MacBook... Yeah, that's not going to fly.

http://mobile.twitter.com ?

I had no idea. I'm going to try switching to this.

Re: New Twitter Has Become Browser Poison

#30

Post by naner »

ComputerGuru wrote: post #13
epi0Bauqu wrote: post #10

I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas after a day it is consuming about half a gig of memory, forcing me to kill and restart.

Firefox has crazy memory leaks. Don't blame it on twitter, regardless how bad their code may be. A tab should be completely and utterly destroyed when refreshed. It doesn't matter how much memory it used, refreshing it or navigating away from that page should (ignoring optimizations, caching, etc. etc. etc.) be like you were never there. Just look at the hundreds of complaints here: http://neosmart.net/blog/2008/fire…

Firefox has crazy memory leaks.

Proof? This was the case with Firefox 2 but now it just seems like this is part of their reputation and is not necessarily grounded in fact.

Post reply on HN