Lightbox slow - anyone else or just me?

FergusonFerguson Registered Users Posts: 1,345 Major grins
edited March 5, 2016 in SmugMug Support
Has anyone noticed the lightbox, and specifically going left/right in it, is very slow of late. For the last week or so, the images in the lightbox paint at what almost looks like dialup speed.

My connection remains nicely fast. It tests at 124/21 locally, and I tested it all the way to San Francisco and it tested at 50/20 with 84ms and 1ms jitter. The collage landscape scrolls more or less at normal speed (occasionally it will pause briefly).

And the lightbox is instant if it's cached, if it is an image I recently looked at.

But others can take 0-30 seconds to completely paint, and looks rather erratic. Some are instant (even ones not cached), but some are top-down, slow and then obviously do some kind of interlaced paint where it goes from blurry to sharp.

I've tried both Chrome and IE.

Smugmug status always shows no issue when I check it.

Anyone else seeing this?

Comments

  • leftquarkleftquark Registered Users, Retired Mod Posts: 3,784 Many Grins
    edited January 16, 2016
    We did switch CDN's recently but there shouldn't be any speed decreases. I'll ask around and see if I can find anything
    dGrin Afficionado
    Former SmugMug Product Team
    aaron AT aaronmphotography DOT com
    Website: http://www.aaronmphotography.com
    My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
  • sarasphotossarasphotos Registered Users Posts: 3,863 Major grins
    edited January 16, 2016
    I have also noticed more than usual wait time in the lightbox and yesterday or the day before I noticed pictures in the normal gallery loading pixel by pixel which I had never noticed before.

    Cheers, Sar
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 18, 2016
    I guess it can't be wide spread. It's happening less to me but it still happens. It's been less severe, but quite erratic. I uploaded a new gallery to test (to be sure it wasn't cached), and some photos pop up instantly, and some just paint progressively from the top. I took another photographer's gallery at another service with similar size photos (he shoots similar cameras) and those come up near instantly (less than a second). That's a flash viewer unfortunately, but I am showing them full screen on a wide monitor (2650 x 1440).

    I'll keep experimenting, but something is definitely different for me. Geographical issue?
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 18, 2016
    I do have something else to add to this that may be a clue.

    If I open the lightbox by clicking on an image in Collage Landscape, then use the right arrow to cycle through, it is slow. As I write this it is very slow, and paints down from top to bottom and "firms up" in three phases of increasing clarity.

    BUT... if I run the slide show on the same gallery and same screen, and use those right arrows to "hurry" it along, it moves quickly. Well, it still has that 1-2 second transition, but that transition starts quickly and is consistent, and the new image is up quicker there consistently than it is in the lightboox (at least frequently the lightboox is much slower).

    Is there something different about how the CDN's and/or retrieval of the photos work in the gallery slideshow (the default one from clicking "slideshow") and how the retrieval works when using the right arrow in the lightboox? The look is identical of the screen, but it's obviously a bit different as one has a slow transition.
  • CastleRockCastleRock Registered Users Posts: 1 Beginner grinner
    edited January 25, 2016
    I have been experiencing the same slowness described by Ferguson over the past couple day. It is sporadic and seems to come and go. I thought it might be my internet connection speed but ran some test and that is not the case.
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 26, 2016
    I have had a ticket open with support who referred it to their operations staff. Nothing since.

    For me it is more bad than good. Once in a while it is decent, once in a great while normal. Yesterday it was so bad as to be completely unusable, I'd see 40 seconds to load lightbox and even then it would hang and never complete.

    While I looked at a sniffer for a bit I saw lots of retransmissions and packet losses to cloudflare (their CDN, I think their new CDN). It's not my link per se, other sites and photo sites work fine, I get instant response on them (I'm on a 120/20 mbs link). It's just awful for Smugmug only.

    I'm amazed it is so specific; if it was this bad for everyone people would be screaming. I think Cloudflare is just sick in some locations. Was it Akamai before? Maybe this is a budget service for cost savings?

    When I get some time going to try some other locations around town, see if it's ISP specific or something. But there's clearly a network issue for me, not a server response issue.
  • leftquarkleftquark Registered Users, Retired Mod Posts: 3,784 Many Grins
    edited January 26, 2016
    Looks like the CDN switch hasn't gone live yet ... still under test. We're still doing a little looksy into this issue.
    dGrin Afficionado
    Former SmugMug Product Team
    aaron AT aaronmphotography DOT com
    Website: http://www.aaronmphotography.com
    My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 26, 2016
    leftquark wrote: »
    Looks like the CDN switch hasn't gone live yet ... still under test. We're still doing a little looksy into this issue.

    But... but... why would I see Cloudflare as the target of browser requests then? Aren't they the new one?
    C:\Users\ferguson>nslookup www.captivephotons.com
    Server:  DD-WRT.leferguson.com
    Address:  192.168.128.1
    
    Non-authoritative answer:
    Name:    wc.smugmug.com.cdn.cloudflare.net
    Addresses:  198.41.209.117
              198.41.208.118
              198.41.209.116
              198.41.208.117
              198.41.209.118
    Aliases:  www.captivephotons.com
              domains.smugmug.com
    

    All of these show as IP's owned by Cloudflare:
    You Searched for: 198.41.208.118
    198.41.208.118
    Record Type: IP Address
    
    NetRange:       198.41.128.0 - 198.41.255.255
    CIDR:           198.41.128.0/17
    NetName:        CLOUDFLARENET
    NetHandle:      NET-198-41-128-0-1
    Parent:         NET198 (NET-198-0-0-0-0)
    NetType:        Direct Assignment
    OriginAS:       AS13335
    Organization:   CloudFlare, Inc. (CLOUD14)
    RegDate:        2012-10-09
    Updated:        2015-10-01
    Ref:            http://whois.arin.net/rest/net/NET-198-41-128-0-1
    

    Are they the outgoing CDN?
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 28, 2016
    I have had a ticket open for quite some time, and am hearing absolutely nothing.

    I have confirmed that other people in my general area (just talked to someone about 10 miles away) have the same problem with my photos.

    And none of you are suffering similar problems? It's just me?

    Leftquark, any comment on the CDN change, not-yet, and Cloudflare above I posted?

    This really needs to be fixed, my web site is simply not usable tonight, at least from here. If you go to full screen and browse through photos, it takes 30-40 seconds and even then often fails.

    It is not my computer (tried several) or my internet connection (had other people in the area try it).

    It appears regional. I logged into a client site in Chicago, RDP'd to a windows system there, and browsed from there. It's a little hard to tell as RDP is slow to there, but it was consistently about 3-4 seconds per image, none of the very irregular display I see, and no 40 second display at all.

    And I'm still seeing failures just to ping the CDN. Here's an example:
    C:\Users\ferguson>nslookup www.captivephotons.com
    Server: DD-WRT.leferguson.com
    Address: 192.168.128.1

    Non-authoritative answer:
    Name: wc.smugmug.com.cdn.cloudflare.net
    Addresses: 198.41.209.118
    198.41.208.117
    198.41.208.118
    198.41.209.117
    198.41.209.116
    Aliases: www.captivephotons.com
    domains.smugmug.com


    C:\Users\ferguson>ping -t 198.41.209.118

    Pinging 198.41.209.118 with 32 bytes of data:
    Request timed out.
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Request timed out.
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=42ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=30ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=43ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Request timed out.
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=28ms TTL=55
    Request timed out.
    Reply from 198.41.209.118: bytes=32 time=30ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55
    Reply from 198.41.209.118: bytes=32 time=29ms TTL=55

    I realize you cannot KNOW from the above that is not from my computer, but trust me -- it's not. It fails in this geography, not just me.
  • leftquarkleftquark Registered Users, Retired Mod Posts: 3,784 Many Grins
    edited January 29, 2016
    Relaying from the ops team (I think I have an understanding of all this!):

    We did get a report of daily peak slowness between Cmcast and CloudFlare's Miami node. They did some maintenance yesterday that was supposed to help, but looks like it may not have solved the problem.

    Can you send along the output of: http://cmac.smugmug.com/cdn-cgi/trace
    (you can replace cmac.smugmug.com with the SM or custom domain being used, for example: http://www.captivephotons.com/cdn-cgi/trace)

    If that isn't loading then there's probably some networking issue, so a traceroute+ping would be useful:

    traceroute cmac.smugmug.com
    ping -c 120 cmac.smugmug.com

    Finally, if you're really feeling fancy this chrome extension shows the ray-id from the headers, which can sometimes be useful. You can look in chrome->view->developer tools->network, browse around until you hit something slow, and send us the headers for the slow resource (if it's just a sporadic slowness)
    dGrin Afficionado
    Former SmugMug Product Team
    aaron AT aaronmphotography DOT com
    Website: http://www.aaronmphotography.com
    My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 29, 2016
    Thanks, Leftquark. Will put that into the next reply, but any idea why the hero's just stopped answering?

    Initial question 1/19 @ 9:47pm ET answered quickly at 1/19 @ 9:59pm saying turning over to ops.

    Followup query 1/20 @ 3:38pm ET - no reply
    Followup query 1/24 @ 7:43pm ET - no reply
    Followup query 1/28 @ 10:22pm ET - no reply

    I vastly appreciate that you come to the forums, but really we shouldn't have to do this all in public to get attention, why are they not answering emails?

    (Yes, I've checked my junk folder, not there either).

    Answers to your questions coming up.
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 29, 2016
    First, this morning (1/29) as I write this, performance is decent. Not good, not normal, but 2-4 seconds for a large image to come up, and no failures. I will try to do it again if it gets worse.

    Output of trace:
    fl=17f41
    h=www.captivephotons.com
    ip=73.54.54.22
    ts=1454081531.844
    visit_scheme=http
    uag=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36
    colo=MIA
    spdy=off
    loc=US
    

    Traceroute
    C:\WINDOWS\system32>tracert cmac.smug.com
    
    Tracing route to cmac.smug.com [72.52.4.119]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  DD-WRT.leferguson.com [192.168.128.1]
      2     8 ms     8 ms     9 ms  96.120.50.173
      3     8 ms     8 ms     8 ms  te-8-1-ur01.southwest.fl.naples.comcast.net [68.85.96.73]
      4    12 ms    10 ms    10 ms  te-0-15-0-0-ar03.bonitasprngs.fl.naples.comcast.net [68.85.238.49]
      5    13 ms    15 ms    15 ms  be-33661-cr01.miami.fl.ibone.comcast.net [68.86.94.89]
      6    13 ms    13 ms    13 ms  ae12.edge2.Miami1.level3.net [4.68.127.205]
      7    38 ms    39 ms    38 ms  ae-1-60.edge3.Washington4.Level3.net [4.69.149.18]
      8    39 ms    38 ms    43 ms  ae-1-60.edge3.Washington4.Level3.net [4.69.149.18]
      9     *        *        *     Request timed out.
    ....repeats up to
     30     *        *        *     Request timed out.
    
    Trace complete.
    

    Ping (and please note that in prior replies there were a lot missing so it is better right now)
    ferguson@zm:~$ ping -c 120 cmac.smugmug.com
    PING wc.smugmug.com.cdn.cloudflare.net (198.41.208.118) 56(84) bytes of data.
    64 bytes from 198.41.208.118: icmp_seq=1 ttl=55 time=30.1 ms
    64 bytes from 198.41.208.118: icmp_seq=2 ttl=55 time=29.5 ms
    64 bytes from 198.41.208.118: icmp_seq=3 ttl=55 time=28.7 ms
    64 bytes from 198.41.208.118: icmp_seq=4 ttl=55 time=31.0 ms
    [COLOR="Red"]64 bytes from 198.41.208.118: icmp_seq=5 ttl=55 time=31.7 ms
    64 bytes from 198.41.208.118: icmp_seq=7 ttl=55 time=30.6 ms[/COLOR]
    64 bytes from 198.41.208.118: icmp_seq=8 ttl=55 time=30.5 ms
    64 bytes from 198.41.208.118: icmp_seq=9 ttl=55 time=32.2 ms
    64 bytes from 198.41.208.118: icmp_seq=10 ttl=55 time=26.9 ms
    64 bytes from 198.41.208.118: icmp_seq=11 ttl=55 time=29.3 ms
    64 bytes from 198.41.208.118: icmp_seq=12 ttl=55 time=32.2 ms
    64 bytes from 198.41.208.118: icmp_seq=13 ttl=55 time=26.2 ms
    64 bytes from 198.41.208.118: icmp_seq=14 ttl=55 time=31.5 ms
    [COLOR="Red"]64 bytes from 198.41.208.118: icmp_seq=15 ttl=55 time=32.3 ms
    64 bytes from 198.41.208.118: icmp_seq=17 ttl=55 time=31.6 ms[/COLOR]
    64 bytes from 198.41.208.118: icmp_seq=18 ttl=55 time=43.4 ms
    64 bytes from 198.41.208.118: icmp_seq=19 ttl=55 time=44.1 ms
    64 bytes from 198.41.208.118: icmp_seq=20 ttl=55 time=31.3 ms
    64 bytes from 198.41.208.118: icmp_seq=21 ttl=55 time=31.1 ms
    64 bytes from 198.41.208.118: icmp_seq=22 ttl=55 time=28.7 ms
    64 bytes from 198.41.208.118: icmp_seq=23 ttl=55 time=28.0 ms
    64 bytes from 198.41.208.118: icmp_seq=24 ttl=55 time=30.5 ms
    64 bytes from 198.41.208.118: icmp_seq=25 ttl=55 time=30.2 ms
    64 bytes from 198.41.208.118: icmp_seq=26 ttl=55 time=28.5 ms
    64 bytes from 198.41.208.118: icmp_seq=27 ttl=55 time=32.3 ms
    64 bytes from 198.41.208.118: icmp_seq=28 ttl=55 time=33.2 ms
    64 bytes from 198.41.208.118: icmp_seq=29 ttl=55 time=30.6 ms
    64 bytes from 198.41.208.118: icmp_seq=30 ttl=55 time=28.1 ms
    64 bytes from 198.41.208.118: icmp_seq=31 ttl=55 time=37.6 ms
    64 bytes from 198.41.208.118: icmp_seq=32 ttl=55 time=27.6 ms
    64 bytes from 198.41.208.118: icmp_seq=33 ttl=55 time=40.9 ms
    64 bytes from 198.41.208.118: icmp_seq=34 ttl=55 time=30.9 ms
    64 bytes from 198.41.208.118: icmp_seq=35 ttl=55 time=30.0 ms
    64 bytes from 198.41.208.118: icmp_seq=36 ttl=55 time=28.2 ms
    [COLOR="red"]64 bytes from 198.41.208.118: icmp_seq=37 ttl=55 time=25.7 ms
    64 bytes from 198.41.208.118: icmp_seq=39 ttl=55 time=32.4 ms[/COLOR]
    64 bytes from 198.41.208.118: icmp_seq=40 ttl=55 time=31.5 ms
    64 bytes from 198.41.208.118: icmp_seq=41 ttl=55 time=29.5 ms
    64 bytes from 198.41.208.118: icmp_seq=42 ttl=55 time=27.1 ms
    64 bytes from 198.41.208.118: icmp_seq=43 ttl=55 time=30.7 ms
    64 bytes from 198.41.208.118: icmp_seq=44 ttl=55 time=31.0 ms
    64 bytes from 198.41.208.118: icmp_seq=45 ttl=55 time=30.0 ms
    64 bytes from 198.41.208.118: icmp_seq=46 ttl=55 time=31.6 ms
    64 bytes from 198.41.208.118: icmp_seq=47 ttl=55 time=31.3 ms
    64 bytes from 198.41.208.118: icmp_seq=48 ttl=55 time=31.5 ms
    64 bytes from 198.41.208.118: icmp_seq=49 ttl=55 time=50.9 ms
    64 bytes from 198.41.208.118: icmp_seq=50 ttl=55 time=31.3 ms
    64 bytes from 198.41.208.118: icmp_seq=51 ttl=55 time=28.2 ms
    64 bytes from 198.41.208.118: icmp_seq=52 ttl=55 time=31.2 ms
    64 bytes from 198.41.208.118: icmp_seq=53 ttl=55 time=31.7 ms
    64 bytes from 198.41.208.118: icmp_seq=54 ttl=55 time=31.2 ms
    64 bytes from 198.41.208.118: icmp_seq=55 ttl=55 time=30.9 ms
    64 bytes from 198.41.208.118: icmp_seq=56 ttl=55 time=31.5 ms
    64 bytes from 198.41.208.118: icmp_seq=57 ttl=55 time=31.0 ms
    64 bytes from 198.41.208.118: icmp_seq=58 ttl=55 time=31.2 ms
    64 bytes from 198.41.208.118: icmp_seq=59 ttl=55 time=33.9 ms
    64 bytes from 198.41.208.118: icmp_seq=60 ttl=55 time=24.7 ms
    64 bytes from 198.41.208.118: icmp_seq=61 ttl=55 time=27.9 ms
    64 bytes from 198.41.208.118: icmp_seq=62 ttl=55 time=23.0 ms
    64 bytes from 198.41.208.118: icmp_seq=63 ttl=55 time=28.9 ms
    64 bytes from 198.41.208.118: icmp_seq=64 ttl=55 time=24.4 ms
    64 bytes from 198.41.208.118: icmp_seq=65 ttl=55 time=24.9 ms
    64 bytes from 198.41.208.118: icmp_seq=66 ttl=55 time=30.0 ms
    64 bytes from 198.41.208.118: icmp_seq=67 ttl=55 time=30.6 ms
    64 bytes from 198.41.208.118: icmp_seq=68 ttl=55 time=30.7 ms
    64 bytes from 198.41.208.118: icmp_seq=69 ttl=55 time=31.0 ms
    64 bytes from 198.41.208.118: icmp_seq=70 ttl=55 time=29.1 ms
    64 bytes from 198.41.208.118: icmp_seq=71 ttl=55 time=32.3 ms
    64 bytes from 198.41.208.118: icmp_seq=72 ttl=55 time=31.4 ms
    64 bytes from 198.41.208.118: icmp_seq=73 ttl=55 time=29.1 ms
    64 bytes from 198.41.208.118: icmp_seq=74 ttl=55 time=29.4 ms
    64 bytes from 198.41.208.118: icmp_seq=75 ttl=55 time=31.6 ms
    64 bytes from 198.41.208.118: icmp_seq=76 ttl=55 time=31.7 ms
    64 bytes from 198.41.208.118: icmp_seq=77 ttl=55 time=29.1 ms
    64 bytes from 198.41.208.118: icmp_seq=78 ttl=55 time=30.0 ms
    64 bytes from 198.41.208.118: icmp_seq=79 ttl=55 time=30.6 ms
    64 bytes from 198.41.208.118: icmp_seq=80 ttl=55 time=29.1 ms
    64 bytes from 198.41.208.118: icmp_seq=81 ttl=55 time=30.9 ms
    64 bytes from 198.41.208.118: icmp_seq=82 ttl=55 time=27.8 ms
    64 bytes from 198.41.208.118: icmp_seq=83 ttl=55 time=32.1 ms
    64 bytes from 198.41.208.118: icmp_seq=84 ttl=55 time=28.7 ms
    64 bytes from 198.41.208.118: icmp_seq=85 ttl=55 time=41.3 ms
    64 bytes from 198.41.208.118: icmp_seq=86 ttl=55 time=30.8 ms
    64 bytes from 198.41.208.118: icmp_seq=87 ttl=55 time=30.2 ms
    64 bytes from 198.41.208.118: icmp_seq=88 ttl=55 time=27.7 ms
    64 bytes from 198.41.208.118: icmp_seq=89 ttl=55 time=31.4 ms
    64 bytes from 198.41.208.118: icmp_seq=90 ttl=55 time=30.3 ms
    64 bytes from 198.41.208.118: icmp_seq=91 ttl=55 time=29.4 ms
    64 bytes from 198.41.208.118: icmp_seq=92 ttl=55 time=24.3 ms
    64 bytes from 198.41.208.118: icmp_seq=93 ttl=55 time=29.4 ms
    64 bytes from 198.41.208.118: icmp_seq=94 ttl=55 time=29.8 ms
    64 bytes from 198.41.208.118: icmp_seq=95 ttl=55 time=26.4 ms
    64 bytes from 198.41.208.118: icmp_seq=96 ttl=55 time=25.1 ms
    64 bytes from 198.41.208.118: icmp_seq=97 ttl=55 time=21.9 ms
    64 bytes from 198.41.208.118: icmp_seq=98 ttl=55 time=30.3 ms
    64 bytes from 198.41.208.118: icmp_seq=99 ttl=55 time=34.3 ms
    64 bytes from 198.41.208.118: icmp_seq=100 ttl=55 time=24.6 ms
    64 bytes from 198.41.208.118: icmp_seq=101 ttl=55 time=31.7 ms
    64 bytes from 198.41.208.118: icmp_seq=102 ttl=55 time=30.2 ms
    64 bytes from 198.41.208.118: icmp_seq=103 ttl=55 time=31.3 ms
    64 bytes from 198.41.208.118: icmp_seq=104 ttl=55 time=31.0 ms
    64 bytes from 198.41.208.118: icmp_seq=105 ttl=55 time=29.9 ms
    64 bytes from 198.41.208.118: icmp_seq=106 ttl=55 time=26.4 ms
    64 bytes from 198.41.208.118: icmp_seq=107 ttl=55 time=31.7 ms
    64 bytes from 198.41.208.118: icmp_seq=108 ttl=55 time=32.2 ms
    64 bytes from 198.41.208.118: icmp_seq=109 ttl=55 time=27.9 ms
    64 bytes from 198.41.208.118: icmp_seq=110 ttl=55 time=32.5 ms
    64 bytes from 198.41.208.118: icmp_seq=111 ttl=55 time=24.8 ms
    64 bytes from 198.41.208.118: icmp_seq=112 ttl=55 time=29.3 ms
    64 bytes from 198.41.208.118: icmp_seq=113 ttl=55 time=29.9 ms
    64 bytes from 198.41.208.118: icmp_seq=114 ttl=55 time=25.8 ms
    64 bytes from 198.41.208.118: icmp_seq=115 ttl=55 time=30.9 ms
    64 bytes from 198.41.208.118: icmp_seq=116 ttl=55 time=28.9 ms
    64 bytes from 198.41.208.118: icmp_seq=117 ttl=55 time=31.1 ms
    64 bytes from 198.41.208.118: icmp_seq=118 ttl=55 time=32.4 ms
    64 bytes from 198.41.208.118: icmp_seq=119 ttl=55 time=36.1 ms
    64 bytes from 198.41.208.118: icmp_seq=120 ttl=55 time=28.1 ms
    
    --- wc.smugmug.com.cdn.cloudflare.net ping statistics ---
    120 packets transmitted, 117 received, 2% packet loss, time 119115ms
    rtt min/avg/max/mdev = 21.952/30.498/50.908/3.872 ms
    
    this chrome extension shows the ray-id from the headers, which can sometimes be useful.

    I installed it, but I doubt it is useful right now as performance is decent. However, right now the ray ID for my site is 26c61f38e9092e9f listed as Miami.

    I also checked and those complaining about performance of my site (who have responded so far) are all on Comcast. It's a small sample set so it may not be that helpful, but Comcast has a huge part of the market here as the other vendor, which is Centurylink DSL, is pretty bad.

    More to follow if it gets bad later today.
  • leftquarkleftquark Registered Users, Retired Mod Posts: 3,784 Many Grins
    edited January 30, 2016
    Ferguson wrote: »
    Thanks, Leftquark. Will put that into the next reply, but any idea why the hero's just stopped answering?

    It looks like your ticket got turned over to the Ops team, and they're not on the desk as frequently as the Heroes are. Sebastian did mention it might take some time for them to respond. Your best bet, in these situations, is to send a separate request in, to get the status. I've asked the heroes to pop onto the ticket and take a peak, though it's good that things appear to be a bit better right now. Let us know if things degrade.
    dGrin Afficionado
    Former SmugMug Product Team
    aaron AT aaronmphotography DOT com
    Website: http://www.aaronmphotography.com
    My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited January 31, 2016
    I waited a bit to answer, but it does seem like it is better. I wish I had been doing something quantitative to measure so I could compare, as it is not as fast as my recollection. But not sure (my recollecting is not as fast as it used to be either).

    So what's the final answer -- is Cloudflare the old, or the new CDN? Did the switchover occur, or is it still coming?
  • leftquarkleftquark Registered Users, Retired Mod Posts: 3,784 Many Grins
    edited January 31, 2016
    Ferguson wrote: »
    So what's the final answer -- is Cloudflare the old, or the new CDN? Did the switchover occur, or is it still coming?

    CloudFlare is the old one. The switchover hasn't occurred yet. I'll make a bigger post when it does!
    dGrin Afficionado
    Former SmugMug Product Team
    aaron AT aaronmphotography DOT com
    Website: http://www.aaronmphotography.com
    My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
  • FergusonFerguson Registered Users Posts: 1,345 Major grins
    edited March 5, 2016
    The problem has returned since yesterday. Same as before. I had been good for quite some time.

    Note I used to go through Miami, now it is all the way up in Atlanta (I am in far SW Florida).

    Cloudfire IP: 198.41.208.117
    Ray ID: 27f2436ec1c40d25

    Trace:
    fl=27f20
    h=www.captivephotons.com
    ip=73.54.54.22
    ts=1457231510.976
    visit_scheme=http
    uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36
    colo=ATL
    spdy=off
    http=http/1.1
    loc=US


    Should I open a ticket, or is this just hopeless with a lame duck CDN?
Sign In or Register to comment.