Cloudflare New Zealand POP to open soon

Forums › New Zealand Broadband › Cloudflare New Zealand POP to open soon

1 | ... | 3 | 4 | 5 | 6 | 7 | 8

timmmay

20365 posts

Uber Geek

Trusted

Lifetime subscriber

#1320546 9-Jun-2015 19:01

A key to using a CDN is setting your HTTP headers appropriately. I set the expiry of rarely changing static assets to at least a month, then if they change I just purge everything - or sometimes I purge a single file.

Using CF speeds up my image rich site hugely - load time comes down from something like 10s to 3s.

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

hio77

'That VDSL Cat'
12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

Subscriber

#1320548 9-Jun-2015 19:02

mercutio:
i did some casual testing a while back. sydney performance seemed to go up and down a lot with small requests of simple pages. (giving 70 msec vs 35 msec or something) whereas auckland was reaslly consistent.

when requesting nz pages from US servers for cache misses performance seems a bit bad. and i have a feeling it's likely to be quite bad in EU...

I think for good page load performance for international audience really have to have a US server to get good performance with Cloudflare, as they pull directly from their origin caches. A long time ago before the Sydney server I found California performance slow and hated how sites were shifting to Cloudflare - this got fixed eventually. But I had a hack prior to push traffic to Texas where it was fast..

That said, there may be a few flaws still, but Cloudflare seems "okay" to me now. And it's quite good in the free level. And definititely seems to be forward looking, and growing in size. So I suspect it'll get better.

If you really want good web page performance you need a CDN that supports PUSH mode, and to push all of your larger files close to the user with long expiry times and renaming of assets rather than expiration.

Kinda getting away from the topic for this thread but anyway...

I actually do recall your posts :)

For the situation i was reffering to, im generally talking rather 5~100MB bz2s, Of which do have long caches (source engine works off a filename exists, dont download logic so "updated" files can never be a thing anyway) Along with rules to boost their cacheability on cloudflares side

I would prefer to push content out to a CDN network rather than just trust on cloudflare caching, but its a cost to performance situation.

Origin server sometimes goes down (nullroutes on that subnet comes up every so often) For the most part Its more for a layer between origin server and traffic that cloudflare is used for - think masses of devnulled wgets.... the scriptkiddies are rather infrequent compared to my last community however.

At some point i need to move our origin server out of its current hosting, shared hosting and into its own dedicated hosting on a bigger port for bursts.

sidenote i must point out, before anyone jumps, No i dont expect cloudflare to handle attacks.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

timmmay

20365 posts

Uber Geek

Trusted

Lifetime subscriber

#1320816 10-Jun-2015 07:36

hio77: Kinda getting away from the topic for this thread but anyway...

I actually do recall your posts :)

For the situation i was reffering to, im generally talking rather 5~100MB bz2s, Of which do have long caches (source engine works off a filename exists, dont download logic so "updated" files can never be a thing anyway) Along with rules to boost their cacheability on cloudflares side

I would prefer to push content out to a CDN network rather than just trust on cloudflare caching, but its a cost to performance situation.

Origin server sometimes goes down (nullroutes on that subnet comes up every so often) For the most part Its more for a layer between origin server and traffic that cloudflare is used for - think masses of devnulled wgets.... the scriptkiddies are rather infrequent compared to my last community however.

At some point i need to move our origin server out of its current hosting, shared hosting and into its own dedicated hosting on a bigger port for bursts.

sidenote i must point out, before anyone jumps, No i dont expect cloudflare to handle attacks.

CloudFlare is a CDN, it does keep websites online if they go offline, and it does handle attacks.

freitasm

BDFL - Memuneh
78920 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1320820 10-Jun-2015 07:55

Once content is cached it should be pretty fast to serve - only first access needs to go back to the origin server. If it's going back for every static content (images, CSS, scripts) then your server is sending out the wrong headers or you have wrong rules in the CDN.

My technology disclosure

gzz392

5 posts

Wannabe Geek

#1320912 10-Jun-2015 09:39

My Cloudflare hosted sites are still routed to Sydney on Spark.

Is there any timeframe at all?

Talkiet

4786 posts

Uber Geek

Trusted

#1320926 10-Jun-2015 09:49

gzz392: My Cloudflare hosted sites are still routed to Sydney on Spark.

Is there any timeframe at all?

We currently don't have a timeframe (or a decision) to connect locally to Cloudflare. We are however upgrading some other CDNs at the moment and adding hundreds of Gbps to local CDN capacity.

Cheers -N

Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.

hio77

'That VDSL Cat'
12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

Subscriber

#1322049 10-Jun-2015 12:40

timmmay:
CloudFlare is a CDN, it does keep websites online if they go offline, and it does handle attacks.

Sure, cloudflare are designed to take it but that doesnt mean im going to be arrogant and expect them to take it.

cloudflare do have their limits...

freitasm: Once content is cached it should be pretty fast to serve - only first access needs to go back to the origin server. If it's going back for every static content (images, CSS, scripts) then your server is sending out the wrong headers or you have wrong rules in the CDN.

was more referring to when we have the likes of SYD, MLB and ALK all pull off a 100mbit port, for a new very large file, it slows down a bit... Once its in their System its there to stay.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

1 | ... | 3 | 4 | 5 | 6 | 7 | 8