Overcome Agile Performance Challenges & Scale to Meet Increasing User Demands
Jun. 15, 2017•0 likes•962 views
Download to read offline
Report
Business
In this webinar you'll learn:
The 3 performance tests every Agile company should be running.
An introduction to the theory behind load testing your applications.
What load curves look like & how to evaluate them.
14. 1414 www.apicasystems.com
Continuous Ramp-up
Single test, slowly increasing traffic to find
practical performance thresholds
• Find the thresholds to trigger auto-scaling
• Include server performance metrics
• Perfmon/Sysstat agent on app server
• APM integration
16. 1616 www.apicasystems.com
Concurrency Tests
Realistic traffic to find performance
endurance & degradation
• Simulate average traffic
• Run a combination of load tests that simulate realistic traffic
• Concurrency Tests against auto-scaling environments can test
scaling response times
21. 2121 www.apicasystems.com
Ask for a Demo!
Doug McAfee
Solutions Engineer
Doug.McAfee@apicasystem.com
Troy Presley
Principal Solutions Architect
Troy.presley@apicasystem.com
https://wpm.apicasystem.com/
https://loadtest.apicasystem.com
• Learn more about load testing
• Regular testing at scale
• Collaboration with Load Test Portal
• Easy scripting with ZebraTester
25. 2525 www.apicasystems.com
Load Testing Differentiators
Performance testing with 5M+ VUs Deep integrations with CI/CD and APM tools
Scalable Agile
Solving complex technical challenges (streaming, IoT,
legacy apps)
Customer can utilize pure SaaS, Hybrid or full On-Prem
Deployment Advanced Technology
Worldwide PS, Support and Technical infrastructure
reach
Highly skilled professional services team enabling
enterprise businesses
Global Expertise
26. 2626 www.apicasystems.com
• Mega-test capacities: 100GBs – 5m VUs
• Automate tests via CodePipeline & Jenkins
• Central test and scenario repository
• Run and manage tests through GUI or API
• Local Server agents for Windows and Linux
• Plugin support – Protobuf, WebSockets, Binary
Program / DDoS
Apica Load Test Details
28. 2828 www.apicasystems.com
Support & Professional Services
• Full-service projects
• Technical Account Management (TAM)
• Test + Monitor packages
• Complete testing plans
• Global capacity planning
• Best practices implementation
• Industry & competitor benchmarks
Professional Services
• Support teams in US, UK, and Sweden
• Email, phone, and remote access
• Dedicated Technical Account Manager (TAM)
• Escalation to Apica R&D team
• Extensive knowledge portal & academy
• Extensive API documentation
24x7x365 Global Support
Editor's Notes
Together Apica Load test and Synthetic Monitoring can proactively identify issues throughout the Agile process.
You have a LT tool
- Open source
- Enterprise grade
- Or you've downloaded ZT
Take that powerful tool you have and wield it like a pro
---
Can use the same same script to accomplish all of these
Start with known good traffic levels
Run successive tests while doubling the traffic each time
When breaking point is found, you can run tests between the last successful test and this one to find your exact breaking point(s)
Short test
Short ramp time
Duration longer, but not excessive, (long enough to complete loops for test effect) – i.e.. 5 minutes -- not a concurrency test
Tail should be short
Find performance “knee”
Transaction rate or Throughput
Obvious one - Session duration
Other is failure rate
Get fancy and combine both with server perf metrics ;)
What constitutes a failure?
Content verification
HTTP Status checks
General or request specific time limits
Unusual response sizes
PRACTICAL THRESHOLDS
PERF METRICS
APM INTEGRATION
Find full CPU saturation
Find ~80% saturation
** Thresholds to auto scale
Multiple thresholds, multiple tests…
No tail – not important
Use RUM metrics, google analytics to target avg traffic
- What are user levels
- What are think times for each step?
Not TRYING to break this on purpose ---- so pushing avg traffic (but can vary to Reasonably high expected traffic)
- We want to find memory leaks
Perform “what if” tests by either changing the mix of user flows/actions, or increasing the load of one or more of them
At least 3x longer than stress test - same script
Ease on the throttle --- there should be NO failures in the first 10%
Take samples from 90% area – WHAT ARE THE THINK TIMES FOR EACH STEP?
OK 3 types of load tests – so what – back to Release lifecycle
Integration – with continuous delivery - minimize effort insert performance testing in the release cycle
Graph – Simple Page level detail of response times from regularly scheduled load test
If you could Kick off a load test prior to release and automate the results that come back from the test….
You could gate deployments if the any of the issues from those 3 test profiles arises
Apica Load Test – has Apis that allow for integration with the CI/CD tools here and many others, to kick off a tests, or (regularly schedule them from the portal)
Return high level or low level error level resolution detail to gate deployments
Not only execution but also Purpose for Performance Tests in your agile release cycle…
What constitutes a failure?
Content verification
HTTP Status checks
General or request specific time limits
Unusual response sizes