ubbt_POSTS table... keep it as lean ( prune old content if possible )...
or implement a custom solution, like creating a ubbt_POSTS_ARCHIVE table, where you send older posts to...
then a small modification to ubbt_TOPICS to add 1 field 'IS_ARCHIVE'....
that way the ubbt_POSTS table only has current posts and runs lickity split...
i've done this for a couple large forums and it works quite well...
all in all.... it can be done.... but if you can double 2GB to 4GB of RAM, you buy yourself a quick solution
