• A friendly and supportive community, register today. Our forums use a separate account system.

Site Updates 🎄 Merry Christmas MedBud: Our Brand New Server is Live

General updates on development of the MedBud platform as a whole.
Waking up early this morning to the website down, for the second day in a row was a frustrating start to Christmas. We've been incredibly proud to have near perfect uptime over the past 4 years.

In general over the past month we've had to leave up our Cloudflare security check most of the time, with our server being bombarded by high amounts of automated requests. Nothing recently seems to be malicious, though several different parties seem to be trying to run automated scrapes of the website at regular intervals; and in general AI language models are bombarding the website with requests consistently.

The long-term solution is simply rewriting high-resource pages/features to better facilitate the increasing volume of traffic, we already utilise significant caching for performance purposes. However, many of the required changes require rewrites of core functionality, it's a huge overhaul that can only reasonably be completed at the same time as MedBud 2.0 – our mammoth on-going UI redesign, focused on mobile compatibility (expect an announcement in the new year, with major progress made recently).

In the short-term, @GrownHealth has been highlighting issues users are having with Cloudflare security checks which we feel needs solving quickly, so I've decided to brute-force a solution and upgrade our server significantly - something we've wanted to do for months now.

New Server Architecture

1766662620126.png
  • We've moved from an AMD Ryzen 5800X (8 core) to an AMD Epyc 4585PX (16 core) processor, with around a 25-30% uplift on individual core performance (effectively the newer server version of the AMD Ryzen 9950X).
  • We've doubled our server's RAM from 32GB to 64GB.
  • Our public uplink has been upgraded from 1Gb to 2.5Gb (backplane 25Gb).
  • We've moved to newer NVMe drives with over twice the I/O performance, upgrading from PCI-E 3 to 5.
We've also changed daily backup processes, where there's now off-site backups held in two different geographical locations. Our disaster recovery time is now around 1-2 hours.

___

If you're reading this post, you're already live on our new server. While I have already been told off by @Tim Henley for working on Christmas morning, my excuse is that I was waiting on my roast coming up to room temp before it goes in the oven – and sincerely, MedBud deserved the Christmas present too 🎁

Merry Christmas everyone, we're looking forward to the new year.
 
Waking up early this morning to the website down, for the second day in a row was a frustrating start to Christmas. We've been incredibly proud to have near perfect uptime over the past 4 years.

In general over the past month we've had to leave up our Cloudflare security check most of the time, with our server being bombarded by high amounts of amounted requests. Nothing recently seems to be malicious, though several different parties seem to be trying to run automated scrapes of the website at regular intervals; and in general AI language models are bombarding the website with requests consistently.

The long-term solution is simply rewriting high-resource pages/features to better facilitate the increasing volume of traffic, we already utilise significant caching for performance purposes. However, many of the required changes require rewrites of core functionality, it's a huge overhaul that can only reasonably be completed at the same time as MedBud 2.0 – our mammoth on-going UI redesign, focused on mobile compatibility (expect an announcement in the New Year, with major progress made recently).

In the short-term, @GrownHealth has been highlighting issues users are having with Cloudflare security checks which we feel needs solving quickly, so I've decided to brute-force a solution and upgrade our server significantly - something we've wanted to do for months now.

New Server Architecture

1766662620126.png
  • We've moved from an AMD Ryzen 5800X (8 core) to an AMD Epyc 4585PX (16 core) processor, with around a 25-30% uplift on individual core performance (effectively the newer server version of the AMD Ryzen 9950X).
  • We've doubled our server's RAM from 32GB to 64GB.
  • Our public uplink has been upgraded from 1Gb to 2.5Gb (backplane 25Gb).
  • We've moved to newer NVMe drives with over twice the I/O performance, upgrading from PCI-E 3 to 5.
We've also changed daily backup processes, where there's now off-site backups held in two different geographical locations. Our disaster recovery time is now around 1-2 hours.

___

If you're reading this post, you're already live on our new server. While I have already been told off by @Tim Henley for working on Christmas morning, my excuse is that I was waiting on my roast coming up to room temp before it goes in the oven – and sincerely, MedBud deserved the Christmas present too 🎁

Merry Christmas everyone, we're looking forward to the new year.
Merry Christmas to you and all your loved ones.

Thank you ever so much for this site, which has helped me so much in the very short time since I found it. Like me, there are countless people that have really benefited from this site. That is why I happily donated real money to your site and I plan to do so monthly.

If there is anything I can do personally I am so here for it.

Big Bear Hugs and Love
🐻💖🐻
 
We've had a few little bugs to iron out after the move: our medication thumbnails on the forum were broken, image generation on the database was ignoring cropping/positioning, and some issues with uploads – but I've managed to fix everything found so far.

Incredibly impressed with how well our new server is performing, it's managing much higher load with very low resource usage. It was definitely the right upgrade to squeeze in before the New Year!
 
We've had a few little bugs to iron out after the move: our medication thumbnails on the forum were broken, image generation on the database was ignoring cropping/positioning, and some issues with uploads – but I've managed to fix everything found so far.

Incredibly impressed with how well our new server is performing, it's managing much higher load with very low resource usage. It was definitely the right upgrade to squeeze in before the New Year!
Congratulations! It is much faster and a lot less glitches on my Android. I love how smooth it is.

You are doing excellent work! Hurray! 🐻💖🐻
 
A quick snapshot of our server's resource usage, we have so much headroom now.

1767462270131.png

Our RAM usage is high because we utilise in-memory caching for the database and files (similar to a 'RAM disk') , our virtual/pagefile memory usage is high because the 'Elasticsearch' instance which powers our lightening quick searches on the forum loads itself into memory - and we've deferred to virtual memory (stored on our NVMe array). All this caching can be seen on the 'Disk I/O' above being incredibly low with minimal spikes, while our network I/O is consistent - because so much is loaded from system memory without touching persistent storage.

The brief spike seen on the CPU graph above is a flush of cached content for the main database, while our most popular (and demanding) pages were again pre/reloaded for future visitors.

Excuse me geeking out about this a little bit, while I have been doing a lot of performance benchmarking/tuning - I'm still in disbelief how well the server is performing overall, beyond all expectation.
 
A quick snapshot of our server's resource usage, we have so much headroom now.

1767462270131.png

Our RAM usage is high because we utilise in-memory caching for the database and files (similar to a 'RAM disk') , our virtual/pagefile memory usage is high because the 'Elasticsearch' instance which powers our lightening quick searches on the forum loads itself into memory - and we've deferred to virtual memory (stored on our NVMe array). All this caching can be seen on the 'Disk I/O' above being incredibly low with minimal spikes, while our network I/O is consistent - because so much is loaded from system memory without touching persistent storage.

The brief spike seen on the CPU graph above is a flush of cached content for the main database, while our most popular (and demanding) pages were again pre/reloaded for future visitors.

Excuse me geeking out about this a little bit, while I have been doing a lot of performance benchmarking/tuning - I'm still in disbelief how well the server is performing overall, beyond all expectation.
Please, geek out all you want and absolutely celebrate yourself! You really have done an epic and amazing job! Well done you!
 
Back
Top