[troybtj]

I'd SWAG too many/too big attachments stored in database, and/or attachment enhancement add-ons.

ASSUMING This is a Small/Mid-Sized forum (< 50 active users at the same time)

In AdminCP -> vB Options -> Message Attachment Options

• turn "inline display of attachments" OFF
• If you have resizing turned on, that might be eating up a lot as well, try it off
• If you don't have a huge number of attachments, do you have a big attachment in a frequently viewed thread? If so, save it to web root filesystem or photobucket and link to it using img tags.
• Disable all products/addons/hacks/modifications related to attachments.
• Disable images in signatures
• Disable animated .gif avatars

Another possible option to check would be setting *NIX Load Limit to something stupid low, like 0.9, so if it pegs out, it won't get your service shut off. I run a dedicated server for just the forums, it runs at about 0.15 - 0.30 on average with around 30-50 active users. Getting vbulletin alone to fill the process queue above 1 continually for more than a small/midsized forum should need tasks like backup/table repair/etc. (or some add-ons/products...)

If you have hundreds of users online, then it's a bit easier to get the load up pretty quick, it depends on the server processor and storage(disk) speed, as well as how many others are using the server (if using shared hosting, which it sounds like you are).

In control panel home, you see the load level averages right above "quick user finder", add 0.3 to whatever the value is when your forum is disabled for a 'quick fuse overload stop', then you can troubleshoot with a helpful hosting company for which threads/scripts are killing it. A load level of 1 is max 'realtime running' on a single processor, 2 is max for a dual processor, etc.

Once the forum is up and running, work with your hosting provider as you enable/increase each item you changed, and see which one causes it to push the load level continually up.

Disabling attachments completely and hosting images elsewhere sounds like it would completely fix your issue.

Hope this helps! I'll try to check back...