+ All Categories
Home > Technology > JIRA Performance After 300,000 Issues

JIRA Performance After 300,000 Issues

Date post: 14-Dec-2014
Category:
Upload: atlassian
View: 4,154 times
Download: 0 times
Share this document with a friend
Description:
Learn how Autodesk broke the 300,000 issues barrier without impacting performance, keeping excellent uptime, with more than 3000 registered users and average of 1800 concurrent users. In this session you will discover the hardware architecture, system settings and other interesting data from Autodesk experience in the field.
Popular Tags:
48
Transcript
Page 1: JIRA Performance After 300,000 Issues
Page 2: JIRA Performance After 300,000 Issues

JIRA Performance after 300,000 issues"

Claudio Ricardo Ombrella!Senior Technology Architect – Autodesk Development Sàrl – Neuchâtel - Switzerland"

http://www.linkedin.com/pub/claudio-ombrella/0/919/17a

Page 3: JIRA Performance After 300,000 Issues
Page 4: JIRA Performance After 300,000 Issues

Agenda"•  Let’s Get to Know Each Other"•  JIRA at Autodesk"•  JIRA Status and Audit"•  Changes We Implemented and Their Results"•  Process – the Rules of “P”"•  Conclusions "•  Questions and Answers"

Page 5: JIRA Performance After 300,000 Issues

Do you know Autodesk?"

Page 6: JIRA Performance After 300,000 Issues

Probably you know AutoCAD"

Page 7: JIRA Performance After 300,000 Issues

Autodesk in a Nutshell "•  Founded in 1982"•  6800+ employees"•  90 products in 18 languages"•  16 films Academy Award"•  10 mln professional users "•  7 mln consumer users"

•  Revenue: 2.22 billion FY12"•  Markets:"•  Architecture, Engineering,

Environment, Computer Science, Computer Graphics and Animations"

Page 8: JIRA Performance After 300,000 Issues

What about you?"

Page 9: JIRA Performance After 300,000 Issues

JIRA Users & Issues"

Page 10: JIRA Performance After 300,000 Issues

Windows / Linux?"

Page 11: JIRA Performance After 300,000 Issues

JIRA at Autodesk"

Page 12: JIRA Performance After 300,000 Issues

JIRA at Autodesk "

•  2005 – “the year we made contact” – JBoss site"•  2008 – Localization Services migrated Notes to JIRA"•  2009 – Some projects in Global Engineering adopt JIRA"•  2012 – 250,000 issues (Feb 8th), 300,000 issues (May 5th)"

Page 13: JIRA Performance After 300,000 Issues

JIRA at Autodesk - Statistics"

• 302,000+ issues"• 3200+ active users"• 384 projects (340 Agile)"

Page 14: JIRA Performance After 300,000 Issues

JIRA at Autodesk - Infrastructure"

Page 15: JIRA Performance After 300,000 Issues

JIRA Status – Mid 2011"

•  JIRA 4.01 Running on Windows 2008 Server R2"•  Average uptime was 6 to 15 days"

•  Could not assign more than 1248 MB to Java VM"

•  Running on ESX Virtual Farm"

•  Clients"•  90% running on MSIE 8"

Page 16: JIRA Performance After 300,000 Issues

Performance Audit Plan"

PERFORMANCE Server

Client Application

Network

Process

Page 17: JIRA Performance After 300,000 Issues

What Did We Change?"

Page 18: JIRA Performance After 300,000 Issues

Server"

•  Migrated to Linux 64-bit 32GB RAM"•  Next three slides will explain why we made this decision"

•  Virtual server running on VMWare ESX farm"•  Configured as High Priority Pool"

•  6 cores"•  Actually running version 4.4.4 and testing Beta 5.1"

Page 19: JIRA Performance After 300,000 Issues

Java Benchmark – Less is Better"

Page 20: JIRA Performance After 300,000 Issues

Java Benchmark – More is Better"

Page 21: JIRA Performance After 300,000 Issues

Java Benchmark – More is Better"

Page 22: JIRA Performance After 300,000 Issues

Client"

•  Advised users to use Chrome, Firefox and Safari"•  MSIE has the slowest JavaScript engine in the market"

•  Clear browser cache frequently"•  Exclude antivirus on browser cache folder"

Page 23: JIRA Performance After 300,000 Issues

Browser Performance"

Tests by Jacob Gube – Six Revisions

Page 24: JIRA Performance After 300,000 Issues

Application – 12GB RAM to Java VM"

Page 25: JIRA Performance After 300,000 Issues

Application – Activated GZIP "

Page 26: JIRA Performance After 300,000 Issues

Application – GreenHopper Cache"

Page 27: JIRA Performance After 300,000 Issues

Application – Kept MySQL Local "

Page 28: JIRA Performance After 300,000 Issues

Application – SSL Only If Needed"

Page 29: JIRA Performance After 300,000 Issues

Network"

•  Configured SilverPeak for WAN acceleration"•  If you have Packteer - create a Level 5 policy"•  You can also use Riverbed for WAN acceleration"

Page 30: JIRA Performance After 300,000 Issues

Results"

Page 31: JIRA Performance After 300,000 Issues
Page 32: JIRA Performance After 300,000 Issues
Page 33: JIRA Performance After 300,000 Issues
Page 34: JIRA Performance After 300,000 Issues
Page 35: JIRA Performance After 300,000 Issues

What About Process? The Rule of 5 “P”"

Page 36: JIRA Performance After 300,000 Issues

Process"

Proficiency

Proof

Production

Plugins Procrastinate

Proliferate

Page 37: JIRA Performance After 300,000 Issues

Proficiency"

•  Build knowledge about your infrastructure"•  Audit your systems"•  Survey your users"•  Observe new technology trends"

Page 38: JIRA Performance After 300,000 Issues

Proof Production"

•  Never update without testing your production data on a staging environment"

•  Involve your users in the acceptance testing"•  Go live with their consensus"

Page 39: JIRA Performance After 300,000 Issues

Plugins"

•  Never install unsupported or discontinued"•  For commercial ones, have a support contract"•  Install only those that are strictly needed"•  Update plugins on staging first, then production"

Page 40: JIRA Performance After 300,000 Issues

Procrastinate"

•  Do not upgrade “for the press release”"•  Proceed by steps: don’t change in one go, DB, OS,

Application. Let the changes “marinate.”"•  Avoid changes close to important deadlines: product

release, end of quarter."•  Exercise the “change freeze” option."

Page 41: JIRA Performance After 300,000 Issues

Proliferate"

•  Keep users informed:"•  on upcoming system changes"

•  on usage tips – best practices (browsers, settings, etc.)"

•  Newsletter"

Page 42: JIRA Performance After 300,000 Issues

RFC – Request For Change"

•  Track all your changes: allows you to step back in case of problems."•  Record the testing done on

staging environment"•  Document your roll-back

plan"

•  Use an approval workflow"•  Deny implementation in

case of doubt"•  Do maintenance outside

business hours"•  Keep RFC process on

another system, not JIRA"

Page 43: JIRA Performance After 300,000 Issues

RFC – Log"

Page 44: JIRA Performance After 300,000 Issues

RFC – Log"

Page 45: JIRA Performance After 300,000 Issues

Conclusions"

Page 46: JIRA Performance After 300,000 Issues

#summit12

Managing #JIRA Performance is not all about

infrastructure. Also how you manage your enterprise

processes.

Page 47: JIRA Performance After 300,000 Issues

Join me on Linked-in Group JIRA Performance

http://www.linkedin.com/groups?home=&gid=4454622&trk=anet_ug_hm"

Page 48: JIRA Performance After 300,000 Issues

Thank you! [email protected]

http://www.linkedin.com/pub/claudio-ombrella/0/919/17a


Recommended