24GB RAM)SQL Database Server: Windows 2008 R2 with SQLExpress 2012 (free version of SQL). with initial presence and roster updates.10k online 5% cpu20k online 10% cpu (2gb ram used for java in openfire)30k online 15% cpu (2gb ram used for java in openfire)40k online 18% cpu (2gb ram used for java in openfire)79k online 50% cpu (2gb ram used for java in openfire)80k online 4% cpu after no more users logging in and no more roster/presence updates I logged in with spark on my own PC quickly, no delay and roster was updated right away.
Both servers are not using RAID currently just single drives. Open Fire cache was using this extra RAM so I believe the previous tests caused this memory to be used and not released.
When they create their account the php script uses REST to send the proper command to the Open Fire server which creates and manages the users and their rosters.
Without the ability to encrypt the data collected on a VM confidential information will be at risk, therefore versions that do not support encryption are not to be used.
They will need to be continuously updated and changed upon by the community as well as within your own standard.