VaultWiki 3.0.3

Thanks for this update pegasus,
Would you advise setting up a slave database, even if it's on the same physical box?

Unless I'm mistaken, having the slave on the same box (while not ideal for CPU) would still be an improvement due to table/row-locking issues that occur whenever database reads occur. However, keep in mind that every write transaction will need (number_of_slaves + 1) * write_time rather than the standard write-time. But using slaves with vBulletin would only offer an improvement if you had multiple slaves setup, and you used a script to randomly select one for each vBulletin session. Otherwise, you will still have the problem where multiple users are accessing the same database table at once and need to queue. As far as I can tell, you would not get any saving from write-locks because vBulletin doesn't support slaves with delayed updates (you would have login and registration problems).