Wordpress on Vultr 768
-
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/
I used to work for a business that hosted a CMS as well as hundreds of websites and email hosting. Clients were all across the globe, so nightly restarts as well as weekend updates were out of the question. The best time to patch and reboot was Thursday nights, once a month. Having a web farm, or database farm would have reduced overall downtime, but in the end, it wasn't too bad. a couple minutes of downtime per server at the most isn't bad once a month in my opinion. Patching hosts were done less frequently, but that involved zero downtime, as all VMs were migrated to other nodes during the update.
A little modern design can get that to zero downtime no problem.
-
I think you need a larger Vultr server for better performance. Cloudways super fast managed Vultr hosting servers are one clicked managed. You can get any help from their live chat support.
-
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/
A little modern design can get that to zero downtime no problem.
Sure thing, but that would have been a huge undertaking in regards to how applications were written/designed. Starting fresh, no question.
-
@masterarts said in Wordpress on Vultr 768:
I think you need a larger Vultr server for better performance. Cloudways super fast managed Vultr hosting servers are one clicked managed. You can get any help from their live chat support.
Why would I pay more for a server that has less resources per dollar than what Vultr offers directly?
I'm legitimately asking the question, as I have done zero research on Cloudways.
-
Just as a note, I've run a Drupal site on the minimal Vultr instance and it was fine. However it was LEMP (NGINX not Apache). Def wasn't super busy but it did fine.
-
@stacksofplates said in Wordpress on Vultr 768:
Just as a note, I've run a Drupal site on the minimal Vultr instance and it was fine. However it was LEMP (NGINX not Apache). Def wasn't super busy but it did fine.
Good to know. So far, performance is much better since re-install. And memory usage is far better.
-
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/
A little modern design can get that to zero downtime no problem.
Sure thing, but that would have been a huge undertaking in regards to how applications were written/designed. Starting fresh, no question.
Would it? What are you running that wouldn't do that today? Wordpress will sure do that.
-
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/
A little modern design can get that to zero downtime no problem.
Sure thing, but that would have been a huge undertaking in regards to how applications were written/designed. Starting fresh, no question.
Would it? What are you running that wouldn't do that today? Wordpress will sure do that.
Well, my comment was based on what the developers were telling me back then. Specifically, the way the websites (IIS & .NET) and databases (MS SQL) handle individual user "sessions". I'm not saying it couldn't be done, but it was more effort and development time than what the company was willing to invest in at that point in time.
-
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/
A little modern design can get that to zero downtime no problem.
Sure thing, but that would have been a huge undertaking in regards to how applications were written/designed. Starting fresh, no question.
Would it? What are you running that wouldn't do that today? Wordpress will sure do that.
Well, my comment was based on what the developers were telling me back then. Specifically, the way the websites (IIS & .NET) and databases (MS SQL) handle individual user "sessions". I'm not saying it couldn't be done, but it was more effort and development time than what the company was willing to invest in at that point in time.
Oh, the developers screwed up and made a bad application that can't scare properly and then got stuck because scaling and transparent updates are done in the same way. Got it.
But for WordPress, it "just works."
-
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@fuznutz04 said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
Good reading, as well: http://www.smbitjournal.com/2011/02/why-we-reboot-servers/
A little modern design can get that to zero downtime no problem.
Sure thing, but that would have been a huge undertaking in regards to how applications were written/designed. Starting fresh, no question.
Would it? What are you running that wouldn't do that today? Wordpress will sure do that.
Well, my comment was based on what the developers were telling me back then. Specifically, the way the websites (IIS & .NET) and databases (MS SQL) handle individual user "sessions". I'm not saying it couldn't be done, but it was more effort and development time than what the company was willing to invest in at that point in time.
Oh, the developers screwed up and made a bad application that can't scare properly and then got stuck because scaling and transparent updates are done in the same way. Got it.
But for WordPress, it "just works."
More like, it was an older product that was built up over many, many years, and the products were being phased out anyway, and being replaced by a newer product that would scale properly. I left before said product came to market though.
I have no complaints about Wordpress nowadays. Very simple to setup and use. Really a great tool for all user levels.