Originally posted by sparky2
Can you estimate what the top-end would be, in terms of scalability.
Our forum usage has been spiking near 600 concurrent users lately, and the server is BARELY handling it.
Can you estimate what the top-end would be, in terms of scalability.
Our forum usage has been spiking near 600 concurrent users lately, and the server is BARELY handling it.
also note (quoting myself LOL )
remember a few things
1. vB user online concurrently is based on default 15 min cookie and is different from mysql concurrent connections
2. vB currently only can use mysql as a backend but later there will be ports to sybase and postgresql way after vB 3.x has been publicly released
3. mysql, provided it has the right hardware and mysql, php and apache configuration is good for theoretically 1000 - 1500 mysql concurrent connections (latter figure with the mysql rpm binaries) based on single dual cpu server setup (excluding dual, quad p4 xeons which could handle more)
4. this means you can have 1000 vB users online displayed but they actually can use 200 - 700 concurrent mysql max connections since vB shows those 1000 vB users over 15 mins and not the exact same sec, you can have any combination
i.e.
300 members + 700 guests = 1000 vb users online past 15 min, with only 300 - 500 mysql concurrent connections in use
or
500 members + 500 guests = 1000 vb users online past 15min, with 500 - 800 mysql concurrent connections in use
both examples show 1,000 vb users online past 15mins but the latter example could place more load on the server due to more mysql concurrent connection usage
5. hardware isn't the only aspect which determines vB performance, you have to have apache, php and mysql configured optimally - left unoptimised especially mysql's configuration, then even the most powerful hardware will not perform well
6. if you set your vB timeout cookie higher than default 15 mins, you will show more vB users online - so set timeout cookie in vB admin panel to 30 mins, then the vB user online display will show users on in the past 30 mins thereby inflating the vB user online display - generally the higher the cookie timeout, the higher the vB users online to mysql concurrent connections ratio
1. vB user online concurrently is based on default 15 min cookie and is different from mysql concurrent connections
2. vB currently only can use mysql as a backend but later there will be ports to sybase and postgresql way after vB 3.x has been publicly released
3. mysql, provided it has the right hardware and mysql, php and apache configuration is good for theoretically 1000 - 1500 mysql concurrent connections (latter figure with the mysql rpm binaries) based on single dual cpu server setup (excluding dual, quad p4 xeons which could handle more)
4. this means you can have 1000 vB users online displayed but they actually can use 200 - 700 concurrent mysql max connections since vB shows those 1000 vB users over 15 mins and not the exact same sec, you can have any combination
i.e.
300 members + 700 guests = 1000 vb users online past 15 min, with only 300 - 500 mysql concurrent connections in use
or
500 members + 500 guests = 1000 vb users online past 15min, with 500 - 800 mysql concurrent connections in use
both examples show 1,000 vb users online past 15mins but the latter example could place more load on the server due to more mysql concurrent connection usage
5. hardware isn't the only aspect which determines vB performance, you have to have apache, php and mysql configured optimally - left unoptimised especially mysql's configuration, then even the most powerful hardware will not perform well
6. if you set your vB timeout cookie higher than default 15 mins, you will show more vB users online - so set timeout cookie in vB admin panel to 30 mins, then the vB user online display will show users on in the past 30 mins thereby inflating the vB user online display - generally the higher the cookie timeout, the higher the vB users online to mysql concurrent connections ratio
Comment