The race to build the next WordPress(opencomputer.dev)
opencomputer.dev
The race to build the next WordPress
https://opencomputer.dev/blog/the-race-to-build-the-next-wordpress/
21 comments
Do people really prefer to see vCPU pricing in per-second increments? Is this useful for any person?
Presumably no information is conveyed by the first 4 significant digits. And can anybody compare this pricing to e.g. AWS or Google Cloud? I have never known my compute cost to second resolution, so I'd need to do calculations to even ballpark this.
Suggestion: Don't obfuscate the price, just remove it. Clearly you don't really want casual browsers to know how much you're charging[1]. Which: fine, this is the current trend in tech. So just remove the pricing and put your calendar link there as a CTA instead. Be classy. Don't play games with your audience.
1 - anybody who plugs this into a calculator will a) understand why you don't show monthly pricing and b) think this is screamingly expensive. Which reinforces my recommendation to just replace the price with a CTA and your calendar link.
Presumably no information is conveyed by the first 4 significant digits. And can anybody compare this pricing to e.g. AWS or Google Cloud? I have never known my compute cost to second resolution, so I'd need to do calculations to even ballpark this.
Suggestion: Don't obfuscate the price, just remove it. Clearly you don't really want casual browsers to know how much you're charging[1]. Which: fine, this is the current trend in tech. So just remove the pricing and put your calendar link there as a CTA instead. Be classy. Don't play games with your audience.
1 - anybody who plugs this into a calculator will a) understand why you don't show monthly pricing and b) think this is screamingly expensive. Which reinforces my recommendation to just replace the price with a CTA and your calendar link.
There is a useful signal in such a way of indicating pricing: it signals that the billing is done at such a resolution, which, for some workloads, can make a difference compared to say, a minimum increment of an hour or a day. Though I would prefer that you can see the conversion to longer timescales on the page itself.
I thought about that, which is indeed what AWS Lambda does, but one of the pitches here is "Always-on VMs," which is not what Lambda is selling.
For CI/CD Jobs? Yes.
For a VM running for a month? No.
For highly scalable batch tasks? Yes.
For small experiments? Yes.
For Full e2e tests creating a full env and killing it a minute later? yes.
For a VM running for a month? No.
For highly scalable batch tasks? Yes.
For small experiments? Yes.
For Full e2e tests creating a full env and killing it a minute later? yes.
One of the info blocks is headed "Persistent VMs" and suggests "Always-on VMs..."
They are not pitching this for any of the "yes" tasks you identified.
They are not pitching this for any of the "yes" tasks you identified.
The fact that author automatically jumps to “distributed system cloud goodness” has me glazed over.
We don’t need a new Wordpress that subscribes to today’s current tech trends.
“It doesn’t scale well” what does that even mean?
We don’t need a new Wordpress that subscribes to today’s current tech trends.
“It doesn’t scale well” what does that even mean?
It means that the author has no idea what they are talking about.
Probably never heard of Kinsta, for example.
We ran a successful network of about 70 wp installs that had peaks of 8.000 concurrent visitors for hours per day already in 2011/2012.
Our sysadmin at the time deployed the whole thing over 2 server clusters behind a wonderful load balancer he fine tuned on OVH.
Total monthly costs: 800€.
That was 14 years ago. So imagine thinking that wordpress is “behind” in 2026 just because it doesn’t subscribe to the deranged cloud subscription culture that has infected the industry.
Wordpress has heaps of technical and non technical issues to solve (especially in governance), but being server-side ain’t one of them.
That was 14 years ago. So imagine thinking that wordpress is “behind” in 2026 just because it doesn’t subscribe to the deranged cloud subscription culture that has infected the industry.
Wordpress has heaps of technical and non technical issues to solve (especially in governance), but being server-side ain’t one of them.
When you say 8000 concurrent visitors, is that per site or across the 70 installs? And what sorts of sites were they?
Because there's an immense difference when it comes to hosting between a blog/brochure site that is fully cachable and a woocommerce or, worse, social network/LMS/other highly dynamic site.
To be clear though, I'm not advocating for distributed cloud architecture - that sort of stuff is best done on a vertically-scaled server, which can get up to many hundreds of CPUs these days.
Because there's an immense difference when it comes to hosting between a blog/brochure site that is fully cachable and a woocommerce or, worse, social network/LMS/other highly dynamic site.
To be clear though, I'm not advocating for distributed cloud architecture - that sort of stuff is best done on a vertically-scaled server, which can get up to many hundreds of CPUs these days.
They where dynamic publishing sites, so not supercomplicated and absolutely cached to the brim. A big chung of the concurrent visitors (prob like 90%) where on two websites, so two installs.
Ok. Yeah, you could easily have 100k concurrent visitors with that, if the request isn't actually reaching php/WordPress. On e it does, you're down to something like 2-4, maybe 10, requests per cpu core, per second. Depends on the hardware and how the site is configured.
rvz(3)
Yeah, thanks, can you now also give us the downsides?