ASTRAPI

Not tested !

Cloudflare:

Free plan

Huge network

Super optimized with latest technologies

Almost all settings with a simple click

They use encryption on all datacenters

e.t.c

You are welcome 🙂

Just convert them all to Innodb 🙂

Hello

The best thing that you can do is to convert all tables to Innodb .

You will benefit a lot.

Hello @Gauravk

You should plan an upgrade to Centos 7 to get the new compilers and try to use phpfpm + Nginx + tuning everything on the system....

Not something that you can solve easily on a topic...

Hello

This is a storage solution and not direct related with your hosting provider or the control panel that you use.

Please re check the main topic....

Some of the advantages are:

1)Very cheap storage hosting... around 5$ per 1TB

2)Cloud infrastructure that should be more stable

3)No maintenance from your side

4) You can benefit from the partnership with Cloudflare that they have as all your files will move from Wasabi to Cloudflare and from there to your users for free....

5)You can scale easily... need another TB ? No problem you can grow without having to adjust anything....

e.t.c

Great 🙂

Hello

To get an idea you can get 2X your cpu:

Chassis model: dell R730

Processor: 2X Intel® Xeon E5 2640v4 CPU - 16C/32T - 2.6 GHz

Storage: 3 × 500 GB SSD

Memory: 192 GB DDR4 ECC

215 Euro

Then you can get the administration support in different prices that you must agree on what you want and how much you want to pay....

You can get something from 50 Euro up to 150 Euro easily...

It's up to you.

In most cases is not something to worry for.

Many users also prefer to totally block external images linking...

Great 🙂

Yes just change the filesystem....

All info are in the tutorial .....

How long it will take for 20GB it depends from your network speed.... but it should be ok in minutes....

Yes you just need to follow the instructions from Cloudflare ... just change your Nameservers to the ones that Cloudflare recommends you and in a few minutes you will see your domain as an Active...

Remember at your ssl settings it will be good to select the Full SSL option.

Then you can edit/add your dns settings...

Cloudflare should auto detect your existing domain DNS records but it will be good to double check them also...

The tutorial is for using Cloudflare also so you can benefit wit the partner agreement between Wasabi and Cloudflare for unlimited traffic between them and benefit also from the usage of Cloudflare CDN....

Hello

Yes you will need a dns record at Cloudflare.

You must follow all steps in the tutorial to make it work.

please check them again...

For the certificate you just need to select the Full option at Cloudflare....

Hello 🙂

Quote

we have about 300 to 800ms to serve page for guest

TFB and serve a page to guest are two different metrics. A TTFB of 300ms it is in acceptable terms. Maybe not the best but acceptable.

Quote

I've created an html file (https://www.espacioprofundo.com.ar/hola.html) which just displays "Hola" on the screen and the TTFB on several runs is on the 180 ms mark consistently.   Checking the same with the site homepage I get values from 240 to 600 ms. 

That's normal as testing a static page .html is a lot faster than the dynamic homepage. For the dynamic page you must hit your cache method and Mysql before you get the TTFB.

Quote

I know that DigitalOcean (my hosting company) do not have the best TTFB in the market.

There is no such thing, hosting with good or bad TTFB as there are many factors for TTFB. (Check below the different factors).

Quote

I've considered to use cloudfare but all nginx_pagepseed optimizations get lost.

Cloudflare offer all or at least almost all the optimizations of pagespeed and a few more i can say for images and also they have to use resources for that and not use your server resources like cpu,ram etc

I did some tests today and i was not able to hit that issue that Adlago report but maybe that's me and the issue exist or another issue exist that is adding that delay...

I think it will be good also to re post here some info about TTFB as it seems that there are many different understandings for the same thing:

Quote

In this case, I refer to the waiting time as part of the first byte.

The waiting time is related to:

TTFB factors

• Geographically relative source and target distance = how close test/visitor is to your server
• DNS, server connection & response time
• MySQL or database backend performance/settings
• Server hardware

Quote

My host plan is expensive and I expect the host company to fulfill contract parameters

Expensive is not something that will guaranty low TTFB. If they promise you that you will get a low TTFB because you will get a good server, that will never happen as i explain above the factors.

Examples of why it can't be done:

For example if you are hosting your nameservers/DNS: You can't compare that by using a reputable DNS provider like:

If for example your server is at Europe let's say Italy and your visitors in the US you can't get a TTFB at 200ms by hosting yourself your DNS.

Optimization of your Mysql is very important if you are testing a dynamic web site.

Another factor is your ssl certificate. Most users use Let's Encrypt RSA 2048bit  (that is great) but they have for all visitors the same certificate.

But not all visitors use some outdated Android devices and most of them can support more modern and faster certificates like an ECDSA 256bit.

So what i do is having both and let Nginx check which one to serve on each user. Using a new version of openssl also helps. Compiling by using a newer than the default GCC will help also.

There are a ton of little things that can save a few ms left and right but again for me the most important is to have the page rendering finish as soon as possible.

Of course having an expensive server it helps as you will probably get a cpu with some extra instructions set specific for ssl.

There is a lot more than getting an expensive server or get hosting A than hosting B.

So asking from Invision support to improve TTFB alone it will not help as your server should be optimized also very well and for sure you should consider the above TTFB factors. Unless that is a bug in the platform that adds that delay...

That's what i get from a client of me:

It never goes more than 150ms.

Thank you 🙂

Yes Cloudflare needs some time to enable the certificate. They have a status indicator and usually is around 10 minutes ...

Also setting the ssl to Full is needed !

Happy new year 🙂

Yes it will be great if there is another way to do that or be able to improve the current code for this 🙂

@diyatv

Nothing changed. It works.

Quote

Just out of curiosity , how long should or could a transfer of only about 20GB take ? Would we be talking days or hours ?

It depends from your network speed but it should get minutes/hours and not days.

Then you are doing something wrong 😞

Yes it works.

Please check again my instructions on first page...

Due to recent rapid growth, we are currently experiencing unforeseen data throughput capacity issues in our us-east-1 data center.

In order to meet the needs of our customers, we are deploying an additional us-east data center (us-east-2) that is planned for operation by 1 October 2019.  

We are also taking steps to improve throughput capacity in us-east-1.  

We do have available throughput capacity in our us-west and eu-central data centers (if those locations are options for your storage use case).  

Hello Vanucci

I don't know. Never tried that.

In general Wasabi Cloud is identical to s3 but i don't know about lambda...

Please check my topic Post #1 as all info are there...

If you are checking just Cloudflare then yes the Cloudflare when is active it will check the requests by the users and will cache your static files like images.

Then it will push the images on there huge network around the world and when another user will request an image that is already on Cloudflare he will take it super fast from the closet to him datacenter and not from your server....

I did update my topic with an easier and safer way to use it 🙂