Quote:
Originally Posted by
nootje 
My macbook is 2.1ghz dual core and only has 1gb of ram, but im not experiencing the issues you are having..Is your version of chrome up to snuff? A couple of versions ago chrome experienced a mem leak and it would show the symptoms you experience. Im running snow leopard btw.
Chrome is version 12.0.742.122, Safari is version 5.0.5 (6533.21.1). AFAIK Chrome is at the latest stable version, because it auto-updates. OS X 10.6.8 Snow Leopard.

This is Safari viewing the new SF, one tab,
52.5% CPU utilisation. It can peak at 80%. and the fans are running at full speed. No other forums do this, except Huddler ones. Maybe the browsers are trying to ping some third-party advert or tracking server which is not responding or is unreachable because I'm in China. Plus there is a heck of a lot of javascript in the new SF pages, perhaps too much.
Pages are still taking around 30 seconds to load, images and avatars are
taking over a minute to load. Compared to the 15 seconds that the old SF took to fully download pages.
For the benefit of anyone who might know about this stuff, this is my Ping and Traceroute to styleforum.net
PING styleforum.net (67.228.167.131): 56 data bytes
64 bytes from 67.228.167.131: icmp_seq=0 ttl=50 time=988.982 ms
64 bytes from 67.228.167.131: icmp_seq=1 ttl=50 time=988.965 ms
64 bytes from 67.228.167.131: icmp_seq=2 ttl=50 time=988.903 ms
64 bytes from 67.228.167.131: icmp_seq=3 ttl=50 time=988.636 ms
64 bytes from 67.228.167.131: icmp_seq=4 ttl=50 time=988.414 ms
64 bytes from 67.228.167.131: icmp_seq=5 ttl=50 time=988.441 ms
64 bytes from 67.228.167.131: icmp_seq=6 ttl=50 time=988.282 ms
traceroute to styleforum.net (67.228.167.131), 64 hops max, 52 byte packets
1 116.115.128.1 (116.115.128.1) 2.303 ms 9.565 ms 10.110 ms
2 116.115.115.69 (116.115.115.69) 9.893 ms 10.503 ms 9.745 ms
3 61.138.69.169 (61.138.69.169) 18.724 ms 10.027 ms 10.043 ms
4 202.99.226.133 (202.99.226.133) 149.420 ms * 19.532 ms
5 219.158.24.145 (219.158.24.145) 18.046 ms 27.544 ms 20.280 ms
6 219.158.4.94 (219.158.4.94) 75.483 ms 81.760 ms 80.735 ms
7 219.158.3.250 (219.158.3.250) 68.899 ms 70.266 ms 70.886 ms
8 219.158.96.250 (219.158.96.250) 70.672 ms 71.601 ms 70.008 ms
9 219.158.29.170 (219.158.29.170) 136.822 ms 137.842 ms 130.389 ms
10 219.158.32.10 (219.158.32.10) 133.647 ms 135.693 ms 140.654 ms
11 los-edge-03.inet.qwest.net (67.14.22.178) 941.213 ms 937.202 ms 978.151 ms
12 208.46.191.210 (208.46.191.210) 941.132 ms 947.220 ms 940.028 ms
13 po5.bbr01.eq01.dal01.networklayer.com (173.192.18.140) 972.803 ms 975.258 ms 980.366 ms
14 po5.dar01.sr01.dal01.networklayer.com (173.192.18.191) 970.942 ms 969.502 ms 970.584 ms
15 po1.fcr04.sr05.dal01.networklayer.com (66.228.118.214) 982.119 ms 981.294 ms 979.982 ms
16 67.228.167.131-static.reverse.softlayer.com (67.228.167.131) 988.592 ms 988.466 ms 990.103 ms
Ping times suddenly jump to almost a second when it gets to the 'qwest.net' line. I do know that a long ping time is bad.
My ISP details:
IP Address: 116.115.141.221
Hostname: 116.115.141.221
IP Country: China
IP Country Code: CHN
IP Continent: Asia
IP Region: Beijing
Guessed City: Beijing
IP Latitude: 39.9289
IP Longitude: 116.3883
Organization: China Unicom Neimeng Province Network
ISP Provider: China Unicom Neimeng Province Network
Quote:
Originally Posted by
nootje 
As for mobiles, i can see where you're coming from, sf cant be browsed on my blackberry anymore, I just get a mem shortage and thats it.
It's a bummer SF is no longer viewable any mobile device, except apparently iPad 2s. A lightweight mobile version of SF is definitely needed here.
Edited by MikeDT - 7/23/11 at 2:46am