When I unveiled the Drupal-powered version of my webcomic to the world, I was proud of what I'd done -- legitimately so, I think. A ten-year-old webcomic, with ten years worth of comic archives, completely converted over to a database-driven site is nothing to sneeze at.
Unfortunately, this pride was short lived: after three days up, my site host provider suspended my account because I was getting too much traffic (thanks, in part, to a link from Drupal's front page) and it was killing the server it was on. They moved me to a test server for about a week, where they monitored how much site resources my site was using... after that week they reported that ubersoft.net had been consuming a full 4% of the site resources, and consquently I'd need to move up, at the very least, to a virtual host provider package.
I had neither the time nor the finances to do this, so I sadly moved back to my static pages. The Drupal version of the site is currently sitting in my test area, while I try to figure out how to redesign it so it can minimize the consumption of site resources.
Since reverting back to the static pages I've been trying to figure out what specifically caused the site to go down. At this point, I think I can point to the following areas:
1. Inaccurate reporting of site hosting capabilities on the part of the provider, and a lack of tools to accurately allow customers to measure site resource usage.
2. Database activity from Drupal on top of standard site resource consumption.
A more complete analysis follows.
DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.
