0

I'm having issues with my current shared hosting provider due to my core database exploding upwards of 1GB due to cache_form. I've been looking at trying to offload the cache and revisions databases into different databases entirely and set them away in order to hold down the load. I think my understanding of how is ok but I want to be sure as this is a current live site.

I declare the default database then declare where each table is explicitly in the prefix array. If this is accurate then I will just do it that way, if not then I'd like to know where I'm going wrong. Do I need to explicitly declare ALL my databases first in settings.php or do I need to declare just my default and let it work that way?

  • 1
    at some point "shared hosting" goes out the window and you should pay more for a dedicated server -- it sounds like you've reached that point. – tenken Dec 11 '13 at 21:21
  • I can't afford the kind of cash a vps requires right now. – CW Smith Dec 11 '13 at 21:24
  • As an aside, do you have cron running? – mpdonadio Dec 11 '13 at 21:45
  • I have cron running. I have OptimizeDB module set to flush out the cache every time cron runs on Drupal. I'm not sure how to configure a cron job in cpanel for it to do it there, but that is what I have right now. – CW Smith Dec 11 '13 at 21:54
0

I think I figured out what to do in order to pull this off. The issue was that the documentation in default.settings.php was rather lacking but I managed to piece it together. You do have to set your tables up explicitly and your databases as well. It has not helped the issue at all, and frankly it concerns me due to the issues with Drupal 8 coming that frankly might not be usable. So I'm going to pursue a different course of action on this.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.