As per the Quickr Wiki ( http://www-10.lotus.com/ldd/lqwiki.nsf/dx/20052009045545WEBCGW.htm ): "This document contains the presentation from Quickr masterclass covering planning optimal deployments – crawl/walk/run. Discussing simplistic deployment architectures which can be linearily scaled over time (e.g. from POC to simple-non-clustered to clustered) Sharing of key tips/recommendations from SVT and Perf - so as to help avoid expensive crit-sits in the field Tuning for performance, stability and reliability" Please note, I do not claim any ownership of this presentation, just am uploading to allow sharing via the Quickr Blog. Any questions/comments/issues, just let me know!

1. Planning Optimal Quickr Deployments Presented by: Norman McBride SVT Reliability, Dublin Software Lab

3. Planning and Preparing for your Deployment.

4. Planning is an essential step: If you Fail to Plan then Plan to Fail !!

5. Planning should be based on the intended short term use of the deployment and the possible future long term use of the system to avoid future performance and reliability issues and possible re-deployment at a later stage.

9. Optimal Hardware as used by SVT in our Test Environment

11. Detailed Hardware and Software requirements can be found at the url below, it is advisable to check these in detail during the planning stage: http://www-01.ibm.com/support/docview.wss?rs=3264&uid=swg27014510

26. Installation Options and Deployment Topologies

27. Installation Options

35. Performance and Tuning Considerations

38. Performance Recommendation for a Clustered Configuration Lotus Quickr Servers 2 Processor/4 GB Memory Database Server 4 processor 8 GB Memory Dedicated Storage or disk array Directory Server 2 processor 4 GB Memory Disk array HTTP Servers 2 Processor 4 GB Memory Load Balancer 2 Processor 4 GB Memory Cell Deployment Mgr 2 Processor 4 GB Memory

39. System Specifications in SVT Reliability

62. What do We base Our Recommendations on?

63. Where do our recommendations come from? (Based on various experiences in our labs and our internal deployments)

78. © IBM Corporation 2009. All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. IBM, the IBM logo, DB2, DB2 Universal Database, Lotus, Domino, Quickr, Redbooks and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.