New CDN is Live

leftquark

Howdy all,
As of last night we've switched to our new CDN (Content Delivery Network, which is what allows us to deliver your photos as fast as possible to anywhere in the world). You shouldn't notice any changes, although in some cases your photos may load even faster than before.

Custom Domains are still using the old CDN for the time being.

For sharing photos, if you have a custom domain, any link to a page (like your lightbox or gallery) will always provide a link in the Share Panel to your custom domain. Direct Embed links will point to https://photos.smugmug.com/*.JPG (or PNG or GIF) so that they'll be delivered over https. In the future, when we can provide https for custom domains, we'll switch direct embed links back to using the custom domain. For now, we'd prefer to provide you with link that we can guarantee you can share; if you'd like it to point to your custom domain, you can simply replace photos.smugmug.com with your domain and bypass the CDN).

sarasphotos

This is good, because I've recently noticed load times have varied between acceptable and agonizingly long, especially going into lightbox view. I just checked a random gallery, and while not instantaneous, it's consistently better across the board. Yesterday I would click on one picture and it would take 20 seconds to load and the next two would load right away, then another 20-second one.

Thanks!

leftquark

sarasphotos wrote: »

This is good, because I've recently noticed load times have varied between acceptable and agonizingly long, especially going into lightbox view.

Would you mind letting me know where you're located (feel free to shoot me a Private Message) and which gallery it is. Everything should be super quick, including going into the lightbox. We recently got smarter about what we pre-load (we don't pre-load as many extra sizes that you don't need, which was causing things to be slower than necessary).

denisegoldberg

leftquark wrote: »

Custom Domains are still using the old CDN for the time being.

Will custom domains also be changed at some point in the near future?

--- Denise

leftquark

denisegoldberg wrote: »

Will custom domains also be changed at some point in the near future?

In the future, yes, though probably not "near future".

sarasphotos

ah, I understand - I've got a custom domain, that explains the longer load time. Also, I'm located in Europe, which probably means even a different CDN.

leftquark

sarasphotos wrote: »

Also, I'm located in Europe, which probably means even a different CDN.

The CDN has locations all over the world!

photoclick

I suspect one unfortunate side-effect of the CDN. When replacing the image with a new version (using Smugmug "Replace" tool) the CDN holds onto, caches the previous version of the file for an indeterminate time. If you have the image linked from soemwhere with a direct link - the older version of the image may be served for some time.

Ferguson

OK, I'm confused.

I see you are avoiding names, so I'll just use the first few letters. You moved from CloudF to CloudF, right?

Never mind... hold that thought...

Without a custom domain, you are using the new CDN for everything, both http and https? You are not redirecting http to https for pages, but you honor whichever the user uses. You use https for the photos regardless, though (at least in the page smugmug generates, not talking about the sharing panel), and the photos all come from photos.smugmug.com domain. Right?

But with a custom domain, you are using the old CDN. For them, we can't use https for pages at all, but even so internally photos are shifted to the https and photos.smugmug.com domain (i.e. the IMG tag uses that, inside the A tag which is still the custom domain). Right?

So if the photos, in either case, use photos.smugmug.com, in fact seem to use the same entire SRC line ... how are you using two different CDN's?

Is it just the page structure that's coming from the old CDN for the custom domain users, and the photos are still from the new?

Or am I reading what I see all wrong in the HTML?

Or can I be looking at old HTML from some cached service from old CloudF* and the page IMG tag sources are really different?

Or should I have gone to bed hours ago and I'm just mixed up?

Signed... confused. And not just by the CDN names.

leftquark

Excellent questions Ferguson.

Ferguson wrote: »

New CDN for everything, both http and https? You are not redirecting http to https for pages, but you honor whichever the user uses. You use https for the photos regardless, though (at least in the page smugmug generates, not talking about the sharing panel), and the photos all come from photos.smugmug.com domain. Right?

Yep!

Ferguson wrote: »

But with a custom domain, you are using the old CDN. For them, we can't use https for pages at all, but even so internally photos are shifted to the https and photos.smugmug.com domain (i.e. the IMG tag uses that, inside the A tag which is still the custom domain). Right?

Yep!

Ferguson wrote: »

So if the photos, in either case, use photos.smugmug.com, in fact seem to use the same entire SRC line ... how are you using two different CDN's?

Is it just the page structure that's coming from the old CDN for the custom domain users, and the photos are still from the new?

Yep! Page structure (HTML) is served from the old CDN, and everything else (images, video, etc) are from the new CDN.