Excellent whitepaper on Sametime running in VMware
Category None
IBM and VMware have published a white paper IBM Lotus Sametime Reference Architecture in a VMware Infrastructure 3 Environment.
The White paper is great and covers the following workload simulations:
This workload is fine for IM load but to me it's incomplete. This is the workload that ships with server.load, and it's all about IM, it's missing some key areas where customers feel load. How does the Sametime Meeting Center scale, Audio/Video scaling in meeting, VoIP scaling, P2P video, P2P screenshare, TCSPI scaling , how well does the environment handle resolve requests from thousands of Notes clients etc.
This is all information that should be considered key to a successful deployment of Sametime. The last real information published for scaling in the area of meetings and audio/video in meetings was in a redbook for Sametime 2.0, it even contained a 1-2-3 spreadsheet for helping to calculate your server needs. The redbook
Sametime 7.5.1 - Best Practices for Enterprise Scale Deployment is a great redbook and does contain some information about deployment considerations, using points ot calculate scaling, but it still doesn't give enough low level information about network impact. How well does the Sametime Gateway scale, when can customers expect to max out their gateway?
Sametime isn't a new product, it's celebrating it's 10th birthday this year, surely the engineers know this stuff? This is the kind of information that should be flowing out from IBM towards customers, partners, internal IBM Sales Engineers. Educated customers, partners and engineers can surely only help Sametime?
IBM and VMware have published a white paper IBM Lotus Sametime Reference Architecture in a VMware Infrastructure 3 Environment.
The White paper is great and covers the following workload simulations:
An active, instant messaging user logging in and chatting with another user in rich-text mode
Exchanging about five messages
Each message was approximately 512 bytes long with a 30-second gap between each message.
The workload adding a user to the Contacts list every 24 iterations
Logged out, waiting about ten minutes, and logging in every 12 iterations
This workload is fine for IM load but to me it's incomplete. This is the workload that ships with server.load, and it's all about IM, it's missing some key areas where customers feel load. How does the Sametime Meeting Center scale, Audio/Video scaling in meeting, VoIP scaling, P2P video, P2P screenshare, TCSPI scaling , how well does the environment handle resolve requests from thousands of Notes clients etc.
This is all information that should be considered key to a successful deployment of Sametime. The last real information published for scaling in the area of meetings and audio/video in meetings was in a redbook for Sametime 2.0, it even contained a 1-2-3 spreadsheet for helping to calculate your server needs. The redbook
Sametime 7.5.1 - Best Practices for Enterprise Scale Deployment is a great redbook and does contain some information about deployment considerations, using points ot calculate scaling, but it still doesn't give enough low level information about network impact. How well does the Sametime Gateway scale, when can customers expect to max out their gateway?
Sametime isn't a new product, it's celebrating it's 10th birthday this year, surely the engineers know this stuff? This is the kind of information that should be flowing out from IBM towards customers, partners, internal IBM Sales Engineers. Educated customers, partners and engineers can surely only help Sametime?
| Permalink | 
Comments
Your right, it's time for IBM Lotus Sametime to provide much more tools and information to customers in this area.
-Tim E. Brown
Posted by Tim E. Brown At 10:28:50 PM On 04/09/2008 | - Website - |
Posted by Carl Tyler At 10:49:43 PM On 04/09/2008 | - Website - |
Posted by Wassim At 11:45:36 PM On 04/09/2008 | - Website - |
Posted by Brian Wenzel At 07:48:57 AM On 04/10/2008 | - Website - |
Posted by Mitch A Carlyle At 09:46:45 AM On 04/10/2008 | - Website - |