Waiting for images

Marcel

Marcel

Happily retired
Staff member
Super Mod
I have a fast connection and have found this site to be getting slower and slower at times. Sometimes it works just fine and others I'll be spending my time waiting. Of course, in this day and age, and me not getting any younger, the waiting part is slowly getting to me. This brings me to attending other forums where pages load faster so I can get more information in less time.

I don't know much about websites and servers and I know that this forum has grown a lot since a few years ago, so maybe nothing can be done because of the size of the data or something could be done about it.

One thing I know is that the more it slows down for me, the less I'm inclined to visit...
 
P

paul04

Senior Member
I think the time of day has a lot to do with it, this morning it was taking up to 30 seconds for pages to load, now 4 hours later, and pages open almost instantly.
 
Marcel

Marcel

Happily retired
Staff member
Super Mod
paul04 said:
I think the time of day has a lot to do with it, this morning it was taking up to 30 seconds for pages to load, now 4 hours later, and pages open almost instantly.
Click to expand...
I have the same experience but just don't understand the why. Kind of difficult to know for sure if it is our server or an internet bottleneck or the government spying on mostly all internet connection.
 
R

RocketCowboy

Senior Member
mikew said:
I belong a few other various forums,when i have had enough fighting this one i can go straight on any of the others and have no problems,we need to move away from blaming browsers and sort the problem, members will walk eventually.
Click to expand...

Not disagreeing with you, and hope my response did not sound like I was trying to blame browsers as that wasn't my intent. The CDN piece adds another wrinkle to the troubleshooting, so I was only adding my experience of the problem as well. I'm not sure what pieces get served from the CDN and what actually hits the Nikonites server, but hoped my experience would help shed some light for the guys that fix this stuff.
 
M

mikew_RIP

Senior Member
No problem RC,at the moment its taking between 10 and 20 seconds to make a page change,not long for one change but too long when your doing loads,had enough for now life is short enough,see you later.
 
B

Blacktop

Senior Member
I have some shots I processed today. I put it up on my Flickr. Uploaded normal fast, so it's no browser issue. I keep checking in here to see if it has improved, but it's about the same as this morning.
I'll keep checking tomorrow as well for I really like this forum. It would be a shame to have to abandon it.
 
M

mikew_RIP

Senior Member
Blacktop said:
I have some shots I processed today. I put it up on my Flickr. Uploaded normal fast, so it's no browser issue. I keep checking in here to see if it has improved, but it's about the same as this morning.
I'll keep checking tomorrow as well for I really like this forum. It would be a shame to have to abandon it.
Click to expand...

I feel the same,i click to come on and if it takes the 10-20 seconds to build the first page i go away again,there are a few regular names that are a bit scarce,normally when i log on in the morning there are three pages of unread threads its only been two lately, i think we are already losing members.
 
B

Blacktop

Senior Member
I read 4 posts ,uploaded a few picks and it took almost a half hour. Editing a post is even worse. The worst part is, that the powers be are not saying or acknowledging that there is a problem ,let alone working on a solution.
 
Marcel

Marcel

Happily retired
Staff member
Super Mod
I sincerely hope @jdeg is working on a solution to this S...L...O...W...., very slow page loading. I timed about 15 seconds between the time I click on "what's new" until the actual page loads. It does add up.

I guess this might be a sign to reduce my visits...
 
Michael J.

Michael J.

Senior Member
Oh, today it is really slow. I wait of tomorrow, maybe it is faster than now. One minute to load a page.


Sent from my iPhone5s using Tapatalk
 
N

nickt

Senior Member
Way too slow here in NY too. It doesn't seem to matter if there are images or not. My Chrome browser says waiting for Nikonites down in the lower left during the 15+ second wait.
I did a tracert command and I get this:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Nick>tracert www.nikonites.com

Tracing route to nikonites.com [66.71.253.146]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms L100.PGHKNY-VFTTP-08.verizon-gni.net [96.248.38.1]
3 9 ms 11 ms 9 ms G0-0-4-7.PGHKNY-LCR-22.verizon-gni.net [100.41.198.52]
4 11 ms 8 ms 9 ms 100.41.7.92
5 * * * Request timed out.
6 12 ms 8 ms 10 ms 0.ae3.BR2.NYC4.ALTER.NET [140.222.231.133]
7 10 ms 11 ms 8 ms 204.255.169.2
8 12 ms 8 ms 10 ms ae8.cr1.lga5.us.zip.zayo.com [64.125.26.161]
9 14 ms 14 ms 14 ms v11.ae29.cr1.dca2.us.zip.zayo.com [64.125.31.206]
10 46 ms 28 ms 26 ms ae2.mpr4.atl6.us.zip.zayo.com [64.125.25.46]
11 27 ms 25 ms 25 ms ae4.mpr3.atl6.us.zip.zayo.com [64.125.31.197]
12 31 ms 32 ms 29 ms xe-1-0-0.mpr1.atl1.us.zip.zayo.com [64.125.22.145]
13 31 ms 29 ms 31 ms 208.185.20.126.IPYX-063451-ZYO.above.net [208.185.20.126]
14 28 ms 29 ms 28 ms xe9-2.dist-ac.atl01.coloat.com [184.170.245.86]
15 27 ms 27 ms 28 ms ex2k7srv1.ndnx.net [66.71.253.146]

Trace complete.

I'm not sure what it all means, but I get the 'request timed out' on step 5 every time and that appears to be the biggest time-suck. It takes a good while to continue through that step. The step before and after the delay appear to both be Verizon entities at opposite coasts of the US. Maybe not a Nikonites problem? Any network guys here that know what it all means?
 
R

RocketCowboy

Senior Member
nickt said:
I'm not sure what it all means, but I get the 'request timed out' on step 5 every time and that appears to be the biggest time-suck. It takes a good while to continue through that step. The step before and after the delay appear to both be Verizon entities at opposite coasts of the US. Maybe not a Nikonites problem? Any network guys here that know what it all means?
Click to expand...

Traceroute (and Microsoft's not quite standard version tracert) basically step through the network path by sending a packet that will "time out" at the next step in the chain in order to trigger a response. That's where the time samples in the output come from ... the time between when the packet was sent and when the response was received. The "request timed out" simply means that the device that should have sent an error on the timed out packet did not respond. There are lots of valid reasons for that to happen, so in itself since the rest of the path works that's probably not an issue.

Overall response times on the traceroute don't exceed 31ms, so I don't suspect it to be a network issue to the main server.

I have noticed that at the bottom of each page, the stats indicate MySQL is taking between 8-15%. My suspicion is that MySQL is overloaded and adding the delay to the page loads. That's just my guess, without seeing the back end server load, but those SQL dips would effect every page and would not show up as a problem on network traces. The MySQL server might also be running on it's own server and not collocated on the web server, making the network tracing less conclusive.
 
M

mikew_RIP

Senior Member
RocketCowboy said:
Traceroute (and Microsoft's not quite standard version tracert) basically step through the network path by sending a packet that will "time out" at the next step in the chain in order to trigger a response. That's where the time samples in the output come from ... the time between when the packet was sent and when the response was received. The "request timed out" simply means that the device that should have sent an error on the timed out packet did not respond. There are lots of valid reasons for that to happen, so in itself since the rest of the path works that's probably not an issue.

Overall response times on the traceroute don't exceed 31ms, so I don't suspect it to be a network issue to the main server.

I have noticed that at the bottom of each page, the stats indicate MySQL is taking between 8-15%. My suspicion is that MySQL is overloaded and adding the delay to the page loads. That's just my guess, without seeing the back end server load, but those SQL dips would effect every page and would not show up as a problem on network traces. The MySQL server might also be running on it's own server and not collocated on the web server, making the network tracing less conclusive.
Click to expand...

Thats what i thought:D:confused:
 
N

nickt

Senior Member
RocketCowboy said:
The "request timed out" simply means that the device that should have sent an error on the timed out packet did not respond. There are lots of valid reasons for that to happen, so in itself since the rest of the path works that's probably not an issue.

Overall response times on the traceroute don't exceed 31ms, so I don't suspect it to be a network issue to the main server.
Click to expand...
Thanks for that explanation. Other than running the command, I really didn't understand what it was telling me.
 
Top