Scaling Confluence: From Performance to People - Presentation Transcript
Scaling
Confluence
From performance to people
Tim Colson, SW Architect, Cisco*
*The views expressed in this presentation are mine and do not necessarily reflect the views of Cisco.
1
Who is Tim?
2
Who is Tim?
Geek!
• Microbiology
• Internet Developer
• Systems Architect @ Cisco
2
Who is Tim?
Geek!
• Microbiology
• Internet Developer
• Systems Architect @ Cisco
Collaborator
2
Who is Tim?
Geek!
• Microbiology
• Internet Developer
• Systems Architect @ Cisco
Collaborator
Confluence User since v1.0
2
Why am I here?
500K+
pages?
2004 2005 2006 2007 2008 2009
3
Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
2004 2005 2006 2007 2008 2009
3
Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
Over 70,000 users
2004 2005 2006 2007 2008 2009
3
Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
Over 70,000 users
250,000 pages / 4,000 spaces
2004 2005 2006 2007 2008 2009
3
Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
Over 70,000 users
250,000 pages / 4,000 spaces
~6K active contributors (30d)
2004 2005 2006 2007 2008 2009
3
Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
Over 70,000 users
250,000 pages / 4,000 spaces
~6K active contributors (30d)
~25K total contributors (4yrs)
2004 2005 2006 2007 2008 2009
3
Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
Over 70,000 users
250,000 pages / 4,000 spaces
~6K active contributors (30d)
~25K total contributors (4yrs)
~300-400K views daily 2004 2005 2006 2007 2008 2009
3
SW + HW
Cluster?
Confluence rocks on a single node!
6
SW + HW
Cluster?
Confluence rocks on a single node!
Cluster adds complexity and width
6
SW + HW
Cluster?
Confluence rocks on a single node!
Cluster adds complexity and width
Recommendations
• Version 2.x - Tim says “Meh”
• Version 3.x - Tim says, “Yay!”
6
SW + HW
Cluster?
Confluence rocks on a single node!
Cluster adds complexity and width
Recommendations
• Version 2.x - Tim says “Meh”
• Version 3.x - Tim says, “Yay!”
Approach
• big honkinʼ servers
• separate instances
6
SW
All ur UX belong to us!
7
SW
All ur UX belong to us!
7
SW
User Experience
8
SW
User Experience
Drop down for 3,500 spaces = FAIL!
8
SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
8
SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
8
SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
Approach
8
SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
Approach
• customi[sz]ation (more later), training, policy, configuration
8
SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
Approach
• customi[sz]ation (more later), training, policy, configuration
• feedback to Atlassian
8
SW
Web 2.0 Integration
9
SW
Web 2.0 Integration
Must be bullet proof
9
SW
Web 2.0 Integration
Must be bullet proof
Instability leads to Instability
9
SW
Web 2.0 Integration
Must be bullet proof
Instability leads to Instability
9
SW
Web 2.0 Integration
Must be bullet proof
Instability leads to Instability
Approach: limit exposure
9
User Activity
Macros & Plugins
1-4 macros I get coffee
43%
0 macros
while it loads...
50% then it’s FAST!
>5
7%
Approach: governance / separate instances
12
User Activity
Access Restrictions
13
User Activity
Access Restrictions
Perceived need and fear
13
User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
13
User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
Scalability issue
13
User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
Scalability issue
13
User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
Scalability issue
Approach: training, policy, tricks
13
User Activity
Support
? ? ?? ? ? ? ? ?? ? ?
User Support IT
? ? ?? ? ?
? ? ? ?? ? ?
Approach
• Consolidate requests inside the enterprise
• Feedback to Atlassian
14
Innovation
Rogue Servers
What are they?
Why care?
23
Innovation
Rogue Servers
What are they?
Why care?
Approach
• Embrace them!
• Engage them!
23
Summary
Large scale collaboration is
more than just SW + HW.
Tim Colson
@ gmail/yahoo/me dot com
24
Scaling
Confluence
From Performance to People
Charles Miller
Confluence Architect
Numbers
Average response time (in ms) for various Confluence operations
5,000
3,750
2,500
1,250
0
2.10.3 3.0-beta2
Average response time (in ms) for various Confluence operations (Clustered)
3,000
2,250
1,500
750
0
2.10.3 3.0-beta2
Throughput
2.10.3
3.0-beta2
Throughput
2.10.3
3.0-beta2
Throughput
2.10.3
3.0-beta2
CPU Idle (8 cores)
2.10.3 ~30%
3.0-beta2 ~5%
http://confluence.atlassian.com/display/DOC/Performance+Testing+Scripts
On the Roadmap
• Improved page moving and reordering for
large spaces
• Improvements for instances with large
numbers of spaces
• Improve user management
• Continue to work on performance,
clustering, stability, documentation
Mind the Gap
You Are Going to Need It
• Change Control
• System Monitoring
• Load Testing
• Staged Upgrades
• Tuning
Tuning
• Database
• Application Server
• Operating System
• JVM
• Confluence
Don’t be afraid to ask
for help.
Clustering
User Management
• Number of users and
groups
• Number of groups per
user
• Response time for
external user
management
confluence.atlassian.com
• Operating Large or
Mission Critical
Confluence Installations
• Performance Tuning
• Configuring a Large
Confluence Installation
(These links will be available from the summit wiki)
A good wiki grows — more people and content, uses more
A good wiki grows — more people and content, uses and demands. What begins as a simple experiment in collaboration, explodes into a new Intranet or a mission critical web application. This session focuses on how to architect Confluence for scale and configure it for growing user needs.
Atlassian Speaker: Charles Miller
Customer Speaker: Tim Colson of Cisco
Key Takeaways:
* Best practices in tuning and performance * Administrative tips-and-tricks for improved performance and management * Lessons from customers less
0 comments
Post a comment