Embed Size (px)
DESCRIPTION
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 MillerCustomer Speaker: Tim Colson of CiscoKey Takeaways: * Best practices in tuning and performance * Administrative tips-and-tricks for improved performance and management * Lessons from customers
Citation preview
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
3
Why am I here?
2004 2005 2006 2007 2008 2009
500K+pages?
3
Why am I here?Experience with rapid growth and large scale wiki
2004 2005 2006 2007 2008 2009
500K+pages?
3
Why am I here?Experience with rapid growth and large scale wiki
Over 70,000 users
2004 2005 2006 2007 2008 2009
500K+pages?
3
Why am I here?Experience with rapid growth and large scale wiki
Over 70,000 users
250,000 pages / 4,000 spaces
2004 2005 2006 2007 2008 2009
500K+pages?
3
Why am I here?Experience with rapid growth and large scale wiki
Over 70,000 users
250,000 pages / 4,000 spaces
~6K active contributors (30d)
2004 2005 2006 2007 2008 2009
500K+pages?
3
Why am I here?Experience with rapid growth and large scale wiki
Over 70,000 users
250,000 pages / 4,000 spaces
~6K active contributors (30d)
~25K total contributors (4yrs)
2004 2005 2006 2007 2008 2009
500K+pages?
3
Why am I here?Experience with rapid growth and large scale wiki
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
500K+pages?
Scalable Collaboration
4
Scalable Collaboration
4
SW HW
Scalable Collaboration
4
SW
(User Activity)3
HW
Scalable Collaboration
4
SW
(User Activity)3
ConfigurationHW
Scalable Collaboration
4
SW
(User Activity)3 Innovation
ConfigurationHW
Scalable Collaboration
5
SW(User Activity)3 Innovation
ConfigurationHW
SW + HW
Cluster?
6
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
8
Drop down for 3,500 spaces = FAIL!
SW
User Experience
8
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
SW
User Experience
8
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
SW
User Experience
8
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
Approach
SW
User Experience
8
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
SW
User Experience
8
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
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
Scalable Collaboration
10
SW
Innovation
ConfigurationHW
(User Activity)3
User Activity
Complex Markup
11
{style}{section}{column:width=70%}{panel:borderStyle=solid|borderColor=#e6e6e6|bgColor=#FFFFFF|}{center}h1. *Milestone*{align:center}{table-plus}| !img7.jpg!| milestones |{table-plus}{align}h6. {color:black}Click the +*buttons*+ below {align:center}{section}{section}[!roadmapspic3.bmp!|http://zed.cisco.com/confluence/display/CPDA/Milestones]{align}{include:Team}{toc:minLevel=4}{column}
User Activity
Complex Markup
At risk: UX, Adoption, Collaboration, Support
11
{style}{section}{column:width=70%}{panel:borderStyle=solid|borderColor=#e6e6e6|bgColor=#FFFFFF|}{center}h1. *Milestone*{align:center}{table-plus}| !img7.jpg!| milestones |{table-plus}{align}h6. {color:black}Click the +*buttons*+ below {align:center}{section}{section}[!roadmapspic3.bmp!|http://zed.cisco.com/confluence/display/CPDA/Milestones]{align}{include:Team}{toc:minLevel=4}{column}
User Activity
Complex Markup
At risk: UX, Adoption, Collaboration, Support
Approach: forums, blogs, screen casts
11
{style}{section}{column:width=70%}{panel:borderStyle=solid|borderColor=#e6e6e6|bgColor=#FFFFFF|}{center}h1. *Milestone*{align:center}{table-plus}| !img7.jpg!| milestones |{table-plus}{align}h6. {color:black}Click the +*buttons*+ below {align:center}{section}{section}[!roadmapspic3.bmp!|http://zed.cisco.com/confluence/display/CPDA/Milestones]{align}{include:Team}{toc:minLevel=4}{column}
User Activity
Macros & Plugins
12
0 macros50%
1-4 macros43%
>57%
User Activity
Macros & Plugins
Approach: governance / separate instances
12
I get coffee while it loads... then it’s FAST!
0 macros50%
1-4 macros43%
>57%
User Activity
Access Restrictions
13
User Activity
Access RestrictionsPerceived need and fear
13
User Activity
Access RestrictionsPerceived need and fear
Web site vs. Collaborative space
13
User Activity
Access RestrictionsPerceived need and fear
Web site vs. Collaborative space
Scalability issue
13
User Activity
Access RestrictionsPerceived need and fear
Web site vs. Collaborative space
Scalability issue
13
User Activity
Access RestrictionsPerceived need and fear
Web site vs. Collaborative space
Scalability issue
Approach: training, policy, tricks
13
User Activity
Support
Approach
• Consolidate requests inside the enterprise
• Feedback to Atlassian14
ITUser Support
???? ??
???? ??
? ???? ??
???? ??
Scalable Collaboration
15
SW
(User Activity)3 Innovation
ConfigurationHW
Configuration
Policy affects Usage
16
... or ...
Configuration
Space!
17
Configuration
Space!
17
Scalable Collaboration
18
SW
(User Activity)3 Innovation
ConfigurationHW
Innovation
Good vs. Evil
19
“...technologies are morally neutral
until we apply them.”
- William Gibson
Enterprise Theme
250 authors
35 spaces
2,500 pages
20
Enterprise Theme
250 authors
35 spaces
2,500 pages
20
25,000 authors
3,500 spaces
250,000 pages
Innovation
Theme & Spacemap
21
Innovation
Theme & Spacemap
21
Innovation
Theme & Spacemap
21
Innovation
Metrics & Analytics
Approach: SQL on Confluence DB
22
0
25
50
75
100
2007 2008 2009 2010
ContentCollaboration ?
Innovation
Rogue Servers
23
Innovation
Rogue ServersWhat are they?
23
Innovation
Rogue ServersWhat are they?
Why care?
23
Innovation
Rogue ServersWhat are they?
Why care?
Approach
• Embrace them!
• Engage them!
23
Summary
24
Large scale collaboration is more than just SW + HW.
Tim Colson @ gmail/yahoo/me dot com
Scaling Confluence
From Performance to People
Charles MillerConfluence Architect
Numbers
0
1,250
2,500
3,750
5,000
Average response time (in ms) for various Confluence operations
2.10.3 3.0-beta2
0
750
1,500
2,250
3,000
Average response time (in ms) for various Confluence operations (Clustered)
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
Log Monitoringhttp://confluence.atlassian.com/display/DOC/How+to+audit+Confluence+-+enabling+user+access+logging
{cache}
{future}
Plugin Management
Customi[sz]ation
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)
Talk to us
Talk to us
Talk to us
Talk to us
