Like Paul said, there is no way (well without rewriting half of vBulletin) to avoid this caching in vB 3.x.
Both Paul and your friend are somehow wrong on the memory usage per forum (or they could both be correct ). For each (sub)forum there is some information stored in the cache, you should think about things like Forum Name & Description (longer names/descriptions will use more memory), array of permissions for each usergroup (so more usergroups also mean more memory used), etc...
Next in this calculation is the number of online visitors and the number of pages they load. Each page will load another set of cached items in memory. So in the end it will be Cache Size * Number of Page Loads.
If you purchase vBuletin you will have access to all active versions, including the vBulletin 2.x versions. If you are starting a new board i would however try to avoid starting with an old version like vB 2.x at all costs. I would start by looking into alternatives for using that many forums. Using 2.000 forums is not only bad from a server perspective, but it will also very likely confuse the members and probably even prevent users from registering as they are overwhelmed with the number of forums.
Well, I don't think there is really any way around it. But, is there any way you could calculate the theoretical max for this, assumign 1500 forums? I'm just wondering if upgrading my server's ram to 4GB would be enough or if it would need even more than that.
Also, someone mentioned "thread prefixes".. what does that entail?
09-05-2007, 05:33 PM
). For each (sub)forum there is some information stored in the cache, you should think about things like Forum Name & Description (longer names/descriptions will use more memory), array of permissions for each usergroup (so more usergroups also mean more memory used), etc...
Threaded Mode