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

1. 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

2. Who is Tim?
2

3. Who is Tim?
Geek!
• Microbiology
• Internet Developer
• Systems Architect @ Cisco
2

4. Who is Tim?
Geek!
• Microbiology
• Internet Developer
• Systems Architect @ Cisco
Collaborator
2

5. Who is Tim?
Geek!
• Microbiology
• Internet Developer
• Systems Architect @ Cisco
Collaborator
Confluence User since v1.0
2

6. Why am I here?
500K+
pages?
2004 2005 2006 2007 2008 2009
3

7. Why am I here?
Experience with rapid growth 500K+
and large scale wiki pages?
2004 2005 2006 2007 2008 2009
3

8. 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

9. 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

10. 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

11. 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

12. 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

13. Scalable Collaboration
4

14. Scalable Collaboration
SW HW
4

15. Scalable Collaboration
SW HW
(User Activity)3
4

16. Scalable Collaboration
SW HW Configuration
(User Activity)3
4

17. Scalable Collaboration
SW HW Configuration
(User Activity)3
Innovation
4

18. Scalable Collaboration
SW HW Configuration
(User Activity) 3 Innovation
5

19. SW + HW
Cluster?
6

20. SW + HW
Cluster?
Confluence rocks on a single node!
6

21. SW + HW
Cluster?
Confluence rocks on a single node!
Cluster adds complexity and width
6

22. 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

23. 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

24. SW
All ur UX belong to us!
7

25. SW
All ur UX belong to us!
7

26. SW
User Experience
8

27. SW
User Experience
Drop down for 3,500 spaces = FAIL!
8

28. SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
8

29. SW
User Experience
Drop down for 3,500 spaces = FAIL!
Paging 50,000 users = FAIL!
People search returns 6 of 500 “Tims” = FAIL!
8

30. 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

31. 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

32. 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

33. SW
Web 2.0 Integration
9

34. SW
Web 2.0 Integration
Must be bullet proof
9

35. SW
Web 2.0 Integration
Must be bullet proof
Instability leads to Instability
9

36. SW
Web 2.0 Integration
Must be bullet proof
Instability leads to Instability
9

37. SW
Web 2.0 Integration
Must be bullet proof
Instability leads to Instability
Approach: limit exposure
9

38. Scalable Collaboration
SW HW Configuration
(User Activity)3 Innovation
10

39. User Activity
Complex Markup
{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}
11

40. User Activity
Complex Markup
{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}
At risk: UX, Adoption, Collaboration, Support
11

41. User Activity
Complex Markup
{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}
At risk: UX, Adoption, Collaboration, Support
Approach: forums, blogs, screen casts
11

42. User Activity
Macros & Plugins
1-4 macros
43%
0 macros
50%
>5
7%
12

43. 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

44. User Activity
Access Restrictions
13

45. User Activity
Access Restrictions
Perceived need and fear
13

46. User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
13

47. User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
Scalability issue
13

48. User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
Scalability issue
13

49. User Activity
Access Restrictions
Perceived need and fear
Web site vs. Collaborative space
Scalability issue
Approach: training, policy, tricks
13

50. User Activity
Support
? ? ?? ? ? ? ? ?? ? ?
User Support IT
? ? ?? ? ?
? ? ? ?? ? ?
Approach
• Consolidate requests inside the enterprise
• Feedback to Atlassian
14

51. Scalable Collaboration
SW HW Configuration
(User Activity) 3 Innovation
15

52. Configuration
Policy affects Usage
... or ...
16

53. Configuration
Space!
17

54. Configuration
Space!
17

55. Scalable Collaboration
SW HW Configuration
(User Activity) 3
Innovation
18

56. Innovation
Good vs. Evil
“...technologies are
morally neutral
until we apply them.”
- William Gibson
19

57. Enterprise Theme
250 authors
35 spaces
2,500 pages
20

58. Enterprise Theme
250 authors 25,000 authors
35 spaces 3,500 spaces
2,500 pages 250,000 pages
20

59. Innovation
Theme & Spacemap
21

60. Innovation
Theme & Spacemap
21

61. Innovation
Theme & Spacemap
21

62. Innovation
Metrics & Analytics
100
Content
75
Collaboration ?
50
25
0
2007 2008 2009 2010
Approach: SQL on Confluence DB
22

63. Innovation
Rogue Servers
23

64. Innovation
Rogue Servers
What are they?
23

65. Innovation
Rogue Servers
What are they?
Why care?
23

66. Innovation
Rogue Servers
What are they?
Why care?
Approach
• Embrace them!
• Engage them!
23

67. Summary
Large scale collaboration is
more than just SW + HW.
Tim Colson
@ gmail/yahoo/me dot com
24

68. Scaling
Confluence
From Performance to People

69. Charles Miller
Confluence Architect

70. Numbers

71. Average response time (in ms) for various Confluence operations
5,000
3,750
2,500
1,250
0
2.10.3 3.0-beta2

72. Average response time (in ms) for various Confluence operations (Clustered)
3,000
2,250
1,500
750
0
2.10.3 3.0-beta2

73. Throughput
2.10.3
3.0-beta2

74. Throughput
2.10.3
3.0-beta2

75. Throughput
2.10.3
3.0-beta2

76. CPU Idle (8 cores)
2.10.3 ~30%
3.0-beta2 ~5%
http://confluence.atlassian.com/display/DOC/Performance+Testing+Scripts

77. 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

78. Mind the Gap

79. You Are Going to Need It
• Change Control
• System Monitoring
• Load Testing
• Staged Upgrades
• Tuning

80. Tuning
• Database
• Application Server
• Operating System
• JVM
• Confluence
Don’t be afraid to ask
for help.

81. Clustering

82. User Management
• Number of users and
groups
• Number of groups per
user
• Response time for
external user
management

83. Log Monitoring
http://confluence.atlassian.com/display/DOC/How+to+audit+Confluence+-+enabling+user+access+logging

84. {cache}
{future}

85. Plugin Management

87. Customi[sz]ation

88. 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)

89. Talk to us

90. Talk to us

91. Talk to us

92. Talk to us