Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to Run WordPress completely from RAM

rickconlee.com

Post reply on HN
Print view View original

51–60 of 61 posts

Re: How to Run WordPress completely from RAM

#52

Post by CaptainOfCoit »

progval wrote: post #18
CaptainOfCoit wrote: post #2

Alternatively, copy everything to /dev/shm before launch, call it a day. Now everything is loaded from RAM. Updates involve copying from source directory to /dev/shm then restart.

How is that different from what the article documents?

I guess it's the same, except I expressed it in ~30 words instead of ~2K words, and using 3.2MB less of data to communicate it :)

Re: How to Run WordPress completely from RAM

#54

Post by matt_heimer »

r1ch wrote: post #38
matt_heimer wrote: post #33

Earlier quoted context omitted.

Its not the the data is only cached by Cloudflare in one place, its that it is cached at the edge node nearest to the user that last made the request. Geographically different users will likely hit a completely different edge node that needs to hit your origin to populate its cache. Cloudflare has a free tiered caching option that helped my site. Instead of cache missing on local edge nodes always having to hit the o…

Cloudflare will actually slow down TTFB for small, less popular sites since they don't maintain a keepalive connection to the origin. This means you pay an additional TCP/TLS setup cost from the Cloudflare POP to the origin which is worse than a direct connection. I also tried testing a smart-placed worker and cloudflared, neither of which seemed to help.

They can use keepalive but it's likely the small sites are not getting enough traffic on the edge nodes to maintain the connections.

You don't think taking a small hit on TTFB is a good trade off for the improved scaling that a CDN offers?

Gone are the days that you don't have to worry about bot traffic being a DDOS. An unresponsive site is a lot worse than an extra TCP/TLS setup.

Re: How to Run WordPress completely from RAM

#55

Post by tambourine_man »

DoctorOW wrote: post #31
tambourine_man wrote: post #3

Ironically, Cloudflare is preventing me from reading the site: Sorry, you have been blocked You are unable to access rickconlee.com

Out of curiosity do you know why Cloudflare has blocked you? Browser integrity check, IP reputation, etc? I'm trying to have more lax settings for my static website, and would love to make sure it's as accessible as possible.

No idea. Vanilla desktop and mobile Safari, cable and 5G, all blocked.

Cloudflare Ray ID: 98d7e0b319f3f390

Re: How to Run WordPress completely from RAM

#56

Post by eichin »

egypturnash wrote: post #13

Pagespeed gives this man's site a 72: https://pagespeed.web.dev/analysis/https-rickconlee-com/foj4... And my plain ol' wordpress an 83: https://pagespeed.web.dev/analysis/http-egypt-urnash-com/a1r... My site's a WP that I started up in like 2012 and it's been running continuously ever since, it's sitting behind Apache, it's got a cache plugin, nothing special at all.

Never heard of pagespeed before (yeah, lucky 10k etc, but also I'm just not a web dev) and this pointed up some huge easy wins on my image heavy homelab site, so thanks for that (setting `Cache-control` at all, and forcing `img loading="lazy"`.) To shortcut some obvious followups: (a) the pagespeed engine is called "lighthouse" and it's on github (Apache licensed)(b) it's also built in to Chrome DevTools (inspect) but for me it was all the way over on the » section of the toolbar. So you can run it locally on a private/staging site. again, thanks!

Re: How to Run WordPress completely from RAM

#60

Post by theycallmerick »

dvfjsdhgfv wrote: post #40

> It’s mounted in a tmpfs-backed RAMDisk > Because even well-cached files still require filesystem-level permission checks, read cycles, and sometimes fragmentation reassembly. I'd assume tmpfs still requires filesystem-level permission checks, or am I mistaken?

[dead]
Post reply on HN