Need Some Help With a Big Site – Load makes it Unuseable

there is no way to rely on SuperCache because you cant even load the page the first time to cache it.

Have you tried the precache method in SuperCache?

You may also want to delete your revisions: https://www.net4now.com/?p=8974

That should clean up the DB a little.

I have no revisions it is a fresh site with no edits

I should have mentioned the

Post Meta Table is pushing 3 million rows
and like i said at most 10 custom fields per post and only
State>citycat no denominations or size or any tags

I am not sure how I can PreCache it if my host is crashing on the sidebar category menu… maybe I could hardcode it since I use Permalinks… it is a list of 50 states which point to subcats of cities.. I still have not even attempted to put a list of cities in the archives.php above the loop but I probably need to display that there as apposed to the sidebar menu.

I will look into that precache feature maybe i could do it local then upload… but not sure.. but that would be the only way i could.

I have no revisions it is a fresh site with no edits

That doesn’t mean the DB has no revisions, just FYI.

The other option would be to start with less data at first. Cache it, add more, repeat and rinse.

honestly it has no revisions its a direct import from a csv file with no edits.

but anyway
The problem with caching is that I get hit by my host for the number of files i have… I mean caching I might as well just run the csv db through a php script and generate static html because there are going to be just as many or more files…

Actually importing the csv which was an export from a mySQL DB into WordPress added 125 or so mb to the database.

I should probably not use WP for this project and just setup a few tables and php templates and access the original db which is 50 mb.

I would lose some functionality but it might actually function heh

anyway anyone have any ideas Im up for listening

WordPress isn’t ‘not’ handling the size (I have a bigger site – WordPress.COM is bigger and runs WordPress). Your SERVER isn’t up for the job. And since you SAID you don’t want to spend more money on it, you’re kind of screwed.

And if this is true:

The problem with caching is that I get hit by my host for the number of files i have

Then there’s nothing you can really do but get a bigger, better, server. Seriously. You’re having two problems:

1) Your DB server’s too slow to process 215,607 posts
2) Your file server is too small to store the 215,607 cached files.

So your options are:
1) Fewer posts
2) Better server
3) Better caching

Try W3TC, which on some servers allows for APC/memcode caching. But you need a better server that allows for that. Shared hosting is just too small at a certain point.