Google Chrome

[JRod0802]

I've found that this site loads much slower on Google Chrome than on Firefox. It's mostly on loading actual threads rather than the menus. I've tested this on two separate computers. I think it all started around the time the "Tweet" option was added to the bottom of each post, which was a few months ago.

Has anyone else noticed this?

[vfx]

I've found that this site loads much slower on Google Chrome than on Firefox. It's mostly on loading actual threads rather than the menus. I've tested this on two separate computers. I think it all started around the time the "Tweet" option was added to the bottom of each post, which was a few months ago.

Has anyone else noticed this?

Yep, the Tweet also started a holdup when posting. That is, after typing, the "Post Quick Reply"does not load and the workaround has to be go to the "Go Advanced" and post from there.

[ElSupreme]

I've found that this site loads much slower on Google Chrome than on Firefox. It's mostly on loading actual threads rather than the menus. I've tested this on two separate computers. I think it all started around the time the "Tweet" option was added to the bottom of each post, which was a few months ago.

Has anyone else noticed this?

Wow I first tried using IE8 (work computer is XP) and it was unusable. Then started using chrome, and is mostly ok. If FF is indeed faster I may have to install it.

[TEG]

Yes, I noticed a big slowdown when Twitter and Facebook links were added. I could see my browser spending more time sending those sites link visit data then actually loading content from here. I made a fuss to the forum operator, who then removed the Facebook links but left the Twitter links. So it is still somewhat slow, but not as bad as it was for a while.

In response to the slowdown I changed my forum settings to show less posts per page which helped, but means I am doing more page stepping than I used to do.

[JRod0802]

In response to the slowdown I changed my forum settings to show less posts per page which helped, but means I am doing more page stepping than I used to do.

Yeah me too. I used to do 100 per page, but now I do 40. Does anyone actually use the "Tweet" button? Is there a way for the moderators to track that?

[de704]

I've found that this site loads much slower on Google Chrome than on Firefox. It's mostly on loading actual threads rather than the menus. I've tested this on two separate computers. I think it all started around the time the "Tweet" option was added to the bottom of each post, which was a few months ago.

Has anyone else noticed this?

But how long does firefox take to open? It's the slowest browser to open, slower that IE, Chrome is the fastest. I could load the TM.com site 10 times before firefox opens.

[AnOutsider]

To be honest, not sure why we need the tweet buttons on each post? Tweet or Like a thread, sure, but not the individual posts?

[NigelM]

I only use Chrome and have zero speed problems....

[dpeilow]

No speed or functionality problems here.

I'm using Chrome on an ancient laptop on XP too.

[JRod0802]

No speed or functionality problems here.

I'm using Chrome on an ancient laptop on XP too.

So it seems like Me, vfx, TEG and maybe ElSupreme are having problems with Google Chrome. NigelM and dpeilow aren't having problems with Chrome.

Do you think it has to do with OS? I'm just trying to narrow it down (software testing is part of my job description at work). I've tested with Vista and Windows 7 and had problems with Chrome. dpeilow tested with XP and had no problems with Chrome.

For those of you that use Chrome, can you post your OS and whether you're having problems or not? Maybe we can get this figured out.

[TEG]

I don't use Chrome. I had noticed the slowdown using Firefox.
It was unusable for me with Facebook+Twitter links.
Now that it has just Twitter, and I have less posts per page it is usable, but not as quick to load as it was before this "social network integration."
If the Twitter links are not doing much good I hope they get removed to speed up loading again.

There must be some other factor in the variability of the slowdown from person to person... Java version? Internet connection speed? Virus scanners? Free memory? Speed of the Twitter cache server local to that user?

[dpeilow]

Quite a few people use the Twitter links.

I thought we'd had this fixed after the topic came up last time.

[NigelM]

For those of you that use Chrome, can you post your OS and whether you're having problems or not? Maybe we can get this figured out.

I have Chrome on Windows 7, am using 20 posts per page, with no problems. HOWEVER, I also use my Kindle Fire sometimes for hanging out surfing from the couch and I've had not problems there either. As far as Internet connection I'm using Verizon Fios 25MBits up and down....

[smorgasbord]

This site is much faster redirecting the following to 127.0.0.1 via etc/hosts:

doubleclick.net
doubleclick.com
googleads.g.doubleclick.net
platform.twitter.com
connect.facebook.net

If you don't understand this message, don't ask how to do it. It can be dangerous.

[AnOutsider]

Adblock plugin helps with the slow ads, though it obviously interferes with the revenue earned by the forum.

[woof]

This site is much faster redirecting the following to 127.0.0.1 via etc/hosts:

doubleclick.net
doubleclick.com
googleads.g.doubleclick.net
platform.twitter.com
connect.facebook.net


I also saw a large slow down on Chrome (on the Mac) back when the twitter stuff was added, so I did the above for just platform.twitter.com. Made a very large difference. Chrome still seems to 'stall' if I open 5 or more tabs from this site at a time. Never bothered to investigate further...just don't do that anymore. I'll add the other sites above and see if that helps.

[Edit] Nope. Still stalls.

[NigelM]

Ran a speedtest just now as I have no problems with loading. Results:


Last Result:
Download Speed: 18470 kbps (2308.8 KB/sec transfer rate)
Upload Speed: 17256 kbps (2157 KB/sec transfer rate)
Tue Feb 21 2012 19:51:50 GMT-0500 (Eastern Standard Time)

P.S. I have no idea if that's helpful....:rolleyes:

[howabout2]

I have NoScript blocking Twitter and Facebook (among other things I don't care for) and therefore don't even see the links. I temporarily allowed scripts from all domains and was shocked by the difference.

If you're using Firefox, don't want to muck with your hosts file or a local caching DNS server, and don't care about Twitter et al, you can grab NoScript and just blacklist twitter.com.

[ElSupreme]

Wow I first tried using IE8 (work computer is XP) and it was unusable. Then started using chrome, and is mostly ok. If FF is indeed faster I may have to install it.


So it seems like Me, vfx, TEG and maybe ElSupreme are having problems with Google Chrome. NigelM and dpeilow aren't having problems with Chrome.

I don't think it is really a Chrome problem, more so my crappy work computer. IE is unuseable on my work computer though. And pretty bad on my home laptop. My desktop can power through anything so I don't notice.

[JRod0802]

I also saw a large slow down on Chrome (on the Mac) back when the twitter stuff was added, so I did the above for just platform.twitter.com. Made a very large difference. Chrome still seems to 'stall' if I open 5 or more tabs from this site at a time. Never bothered to investigate further...just don't do that anymore. I'll add the other sites above and see if that helps.

[Edit] Nope. Still stalls.

Yeah, mine stalls after 4 or 5 too :(

[cinergi]

I'm doing fine with Chrome on Win7 ... haven't noticed anything unusually slow.

[JRod0802]

I have NoScript blocking Twitter and Facebook (among other things I don't care for) and therefore don't even see the links. I temporarily allowed scripts from all domains and was shocked by the difference.

If you're using Firefox, don't want to muck with your hosts file or a local caching DNS server, and don't care about Twitter et al, you can grab NoScript and just blacklist twitter.com.

Thank you! I just got the extension "NotScripts" for Google Chrome and black listed platform.twitter.com and things load about 10 or 15 times faster! I can also view more than 4 or 5 tabs now... I just had 10 open no problem! :biggrin:

Edit: This does screw up Twitter, but I practically never use Twitter anyway.

[SByer]

I'm going to give NotScripts a try as well.

I have to admit, there are couple of bugs (and they're on my plate): http://crbug.com/16581 and http://crbug.com/74721 that make things worse when something slow like the Twitter or Facebook buttons hold things up.

I even got mad enough that I wrote a Chrome extension to scrape the 'new post in thread' links and open them carefully one at a time to minimize the stalls. Should just get better with Twitter blocked. I didn't want to block everything, since I know the ads support the site.

[dpeilow]

People open 4 or 5 tabs to this site at the same time? :confused:


SByer, are you involved with the Honeycomb browser?

[AnOutsider]

People open 4 or 5 tabs to this site at the same time? :confused:


SByer, are you involved with the Honeycomb browser?

Or more. Click new posts, open interesting ones in new window, mark the rest as read, close initial tab, proceed to read. I do the same with google results.

[ElSupreme]

Or more. Click new posts, open interesting ones in new window, mark the rest as read, close initial tab, proceed to read. I do the same with google results.

That is pretty much how I do it. Right now I only open 8 posts at once max. If I have other stuff running it is 6 posts. I keep the main forum site open on an additional tab.

[AnOutsider]

That is pretty much how I do it. Right now I only open 8 posts at once max. If I have other stuff running it is 6 posts. I keep the main forum site open on an additional tab.

I'm ashamed to say, it rarely needs more than 8 tabs for me since I'm on so much :redface:

[mpt]

We put the Tweet-this and Facebook links in over a year ago as a convenience to share an article.

Both pull data directly from their respective systems, Facebook was so dreadful that it was pulled really quickly!

All the tweet buttons take about 700mS for me on a typical page (here in NJ) - looking at the waterfall chart on Safari. That's quite a reasonable chunk of the overall time. Plus, the resource http://platform.twitter.com/widgets/images/t.gif is used to form the tweet payload and so isn't cached.

Looking at the analytics that we've gathered, people do use the tweet buttons (we're grateful for that) but there is more traffic from the 'Auto-tweet' out of the @TeslaMotorsClub account and RT's of that than personal tweeting of a post. I'm happy to drop the per-post tweet control. I'll get to that this week.

Recently, Google have been including some VERY poor performing tracking pixels but I get the sense that they've been removed or repaired. That might explain recent performance issues.

By all means use blocking tools - enough people don't to allow us to get general site analytics.

Use ad. blockers if you wish but the funds do go into a small pot that we'll hopefully be able to use to carry out some bigger site updates this year. Right now, the infrastructure software/hardware/network is covered by me - I'll pass a hat round if it ever becomes an issue :-)

[AnOutsider]

I'll pass a hat round if it ever becomes an issue :-)

Please do, as I've previously said (and I know you're hesitant to set a service level expectation), I'd be happy to donate to the cause of keeping the site afloat and the admins happy.

[woof]

I have to admit, there are couple of bugs (and they're on my plate): http://crbug.com/16581 and http://crbug.com/74721 that make things worse when something slow like the Twitter or Facebook buttons hold things up.

I'm wondering if it's a simultaneous locking for access to the cache type problem. I see a lot of "Waiting for cache" messages, which is odd on a high end Macbook with SSD disks. But I can imaging that having 10+ pages from this site all hitting the cache loading the same small "tweet" icons over and over might cause some contention, and if one is holding the lock at the wrong point (like while waiting for something else to load) it could explain the unresponsiveness until everything is loaded problem.

[TEG]

Maybe twitter feed is just slower in general for some of us.
Even when I visit them directly, I sometimes have performance issues, like this I just saw today:
http://i1182.photobucket.com/albums/x453/tgriner2/twitslow.jpg

[TEG]

People open 4 or 5 tabs to this site at the same time? :confused:

That is how I browse in general.
Perhaps the site isn't designed for hardcore multi-taskers...

[SByer]

SByer, are you involved with the Honeycomb browser?

No. While the Honeycomb browser is still WebKit based, the outer parts of it are something else. I'm not directly involved with Chrome on Android, but do work with some of that team.

[JRod0802]

That is how I browse in general.
Perhaps the site isn't designed for hardcore multi-taskers...

Me too. I typically open all the threads I plan on reading, and then read them all. I find that it saves time. This usually results in ~15 tabs being opened simultaneously though.

[TEG]

This site is much faster redirecting the following to 127.0.0.1...

Indeed it is! :wink:

[mpt]

I moved the tweet button to the top; how does that look and work for everyone?

[Lloyd]

I don't see it at all now, but that's ok with me. IE8

[AnOutsider]

I moved the tweet button to the top; how does that look and work for everyone?

I think that makes sense. You'd likely want to share a topic vs a post anyway


I don't see it at all now, but that's ok with me. IE8

it's above the pagination:

http://easycaptures.com/fs/uploaded/453/7318883511.jpg

[dpeilow]

No. While the Honeycomb browser is still WebKit based, the outer parts of it are something else. I'm not directly involved with Chrome on Android, but do work with some of that team.

Could you pass on that the twitter site itself runs like a dog on there please? It is unusably slow and unresponsive. It is the only website I visit that does this - no idea why.

Running 3.1 on a 32GB Galaxy Tab 10.1

[dpeilow]

I think that makes sense. You'd likely want to share a topic vs a post anyway


Actually, I want to share a post. I know others do it that way too.

If I share a topic, the top post on the page may be months old and then people wonder why I'm sharing it.

[Lloyd]

I think that makes sense. You'd likely want to share a topic vs a post anyway



it's above the pagination:

http://easycaptures.com/fs/uploaded/453/7318883511.jpg

OK, it's there now, I swear it was not earlier. It's ok with me still if it was not there. I don't tweet.

[SByer]

And after trying NotScript for Chrome, I found ScriptNo, which has a better options page, let me put it in 'Allow' mode for a default, and has a convenient 'AntiSocial' checkbox which gets rid of all the little share buttons I don't use.

(For Android browser bugs, there's Report Bugs | Android Open Source (http://source.android.com/source/report-bugs.html) - much better than me not getting the information right).

[mpt]

Ok, I think that I have the best of both worlds; I have a tweet button at the thread level at the top; this fetches the javascript one time - quick. I then have individual post icons on each post that are cached.

[AnOutsider]

Ok, I think that I have the best of both worlds; I have a tweet button at the thread level at the top; this fetches the javascript one time - quick. I then have individual post icons on each post that are cached.

Perfect. You can do the same with Facebook btw, they have a similar sharer URL:
http://www.facebook.com/sharer.php?u=POSTURL&title=TEXTTOPREFILL

[mpt]

Thanks! and done.

...please like us :-)

[SByer]

Ok, seems a reasonable pace to put this.

Chrome has gotten better at opening a ton of tabs at once (I'm on dev channel, M22, but current betas have the fix, and probably current stable), and my typical use pattern for this forum is to go into the New Posts page and Cmd/Ctl-click on the 'go to new post' icon for each thread (I read more threads than I skip, so it makes sense), then I can quickly read a bunch of things without interruption. Given those things, I went ahead and created a bookmarklet that does this for me. It's available at http://marklets.com/OpenNewInTabs.aspx (you can look at the JS, it's pretty simple).

It might actually work in Firefox too. Maybe IE, but I wouldn't bet on it. Besides, y'all are my friends, and friends don't let friends use IE, do they? ;-) (*)


(*) Frustrates me that my wife works at a place where their internal apps still require IS, and crufty old virus magnet versions (<9) at that. Lame.

[vfx]

I keep dozens and dozens of tabs open. Google Chrome's big problem is that on the occasional crash the "restore" button does not show up or sometimes does not work. Arrrrgg

[woof]

I went ahead and created a bookmarklet that does this for me.

And there was much rejoicing!

Thanks so much for this.

[ElSupreme]

Ok, seems a reasonable pace to put this.

Chrome has gotten better at opening a ton of tabs at once (I'm on dev channel, M22, but current betas have the fix, and probably current stable), and my typical use pattern for this forum is to go into the New Posts page and Cmd/Ctl-click on the 'go to new post' icon for each thread (I read more threads than I skip, so it makes sense), then I can quickly read a bunch of things without interruption. Given those things, I went ahead and created a bookmarklet that does this for me. It's available at http://marklets.com/OpenNewInTabs.aspx (you can look at the JS, it's pretty simple).

It might actually work in Firefox too. Maybe IE, but I wouldn't bet on it. Besides, y'all are my friends, and friends don't let friends use IE, do they? ;-) (*)


(*) Frustrates me that my wife works at a place where their internal apps still require IS, and crufty old virus magnet versions (<9) at that. Lame.

Ok I am testing it out. I normally prioritize what I view first but this will help when I am cleaning up threads to skim.

[cinergi]

Ok, seems a reasonable pace to put this.

Chrome has gotten better at opening a ton of tabs at once (I'm on dev channel, M22, but current betas have the fix, and probably current stable), and my typical use pattern for this forum is to go into the New Posts page and Cmd/Ctl-click on the 'go to new post' icon for each thread (I read more threads than I skip, so it makes sense), then I can quickly read a bunch of things without interruption. Given those things, I went ahead and created a bookmarklet that does this for me. It's available at http://marklets.com/OpenNewInTabs.aspx (you can look at the JS, it's pretty simple).

It might actually work in Firefox too. Maybe IE, but I wouldn't bet on it. Besides, y'all are my friends, and friends don't let friends use IE, do they? ;-) (*)


(*) Frustrates me that my wife works at a place where their internal apps still require IS, and crufty old virus magnet versions (<9) at that. Lame.

I've been making heavy use of this. LOVE IT. Makes getting through the new posts so much faster!

[SByer]

Glad you like it! Glad I didn't suffer through learning JavaScript for nothing ;-).

[cinergi]

Looks like Chrome 22 broke this. One link opens in a tab, the rest in new windows. I changed it to emulate a ctrl-click which opens the links in a new tab. I haven't tested across browsers ...
I used this to guide me: How to simulate mouse click using Javascript? - Stack Overflow (http://stackoverflow.com/questions/6157929/how-to-simulate-mouse-click-using-javascript)




javascript:(function(){
var aElems=document.getElementsByTagName('a');
if (document.createEvent) {
for(var i=0;i<aElems.length;++i){
if(aElems[i].href.indexOf('?goto=newpost')>0){
var oEvent = null;
oEvent = document.createEvent('MouseEvents');
oEvent.initMouseEvent('click', true, true, document.defaultView, 0, 0, 0, 0, 0, true, false, false, false, 0, aElems[i]);
aElems[i].dispatchEvent(oEvent);
}
}
}
}
)();

[clea]

thank you, i had been too busy to try and find the problem myself and i had been using it all the time before to keep up with all the traffic.

[cinergi]

Figures -- on a Mac it's not ctrl-click, it's command-click. So the code has to look like this:



oEvent.initMouseEvent('click', true, true, document.defaultView, 0, 0, 0, 0, 0, false, false, false, true, 0, aElems[i]);


(10th param changes to false and 13th to true)