All of these questions are irrelevant to our software. vBulletin is not a server-based application. It is a series of Web Scripts that runs on top of an Web Server and Database Server platform. You would control the use of CPU threads and how the database is saved through the configuration of Apache and MySQL. Not through vBulletin.
You'll need to optimize Apache to properly handle threads. MySQL's documentation has information on where to store the database. You will probably not want to store it in RAM though. That is volatile. An SSD should be sufficient.
vBulletin makes no use of graphics processing that would need any access to a video card. The end-user's browser might since vBulletin's output is just HTML.
You'll need to optimize Apache to properly handle threads. MySQL's documentation has information on where to store the database. You will probably not want to store it in RAM though. That is volatile. An SSD should be sufficient.
vBulletin makes no use of graphics processing that would need any access to a video card. The end-user's browser might since vBulletin's output is just HTML.
Comment