This presentation focused on "Simple ways to Jumpstart a Performance Culture". The presentation aimed to provide insights and practical strategies for creating a performance-driven organizational culture. It will cover key concepts such as setting performance goals, establishing clear performance expectations, providing ongoing feedback, recognizing and rewarding top performers, and creating a continuous improvement mindset. It discussed the importance of leaders in fostering a performance culture, and the role of communication in promoting transparency and accountability. It also included pratical E2E Load Testing examples of a Java APP with k6 using GitHub Actions.

1. Filipe Oliveira
performance <at> redis <dot> com
> simple ways to jumpstart a performance culture

2. Filipe Oliveira
performance <at> redis <dot> com
> why jumpstart <

3. Filipe Oliveira
performance <at> redis <dot> com
> why jumpstart <
security?

4. Filipe Oliveira
performance <at> redis <dot> com
compliance?
> why jumpstart <

5. Filipe Oliveira
performance <at> redis <dot> com
performance?
> why jumpstart <

6. Filipe Oliveira
performance <at> redis <dot> com
> non functional <

7. Filipe Oliveira
performance <at> redis <dot> com
> $1.56
trillion/year *
why <
* Consortium for Information and Software Quality report

8. Filipe Oliveira
performance <at> redis <dot> com
> unlocks opportunities [1] <
[1] https:/
/www-file.huawei.com/-/media/CORPORATE/PDF/mbb/5g-unlocks-a-world-of-opportunities-v4.pdf?la=en

9. Filipe Oliveira
performance <at> redis <dot> com
> unlocks
opportunities [1]
[1] https:/
/www-file.huawei.com/-/media/CORPORATE/PDF/mbb/5g-unlocks-a-world-of-opportunities-v4.pdf?la=en

10. Filipe Oliveira
performance <at> redis <dot> com
“we ship fast”...
…“unnecessary”

11. Filipe Oliveira
performance <at> redis <dot> com
> why now? <

12. Filipe Oliveira
performance <at> redis <dot> com
> why not PROD? <

13. Filipe Oliveira
performance <at> redis <dot> com

14. Filipe Oliveira
performance <at> redis <dot> com
> cost of bug
DEV vs PROD
100X
*Integrating Software Assurance into the Software Development Life Cycle (SDLC)

15. Filipe Oliveira
performance <at> redis <dot> com
> foster a culture <

16. Filipe Oliveira
performance <at> redis <dot> com
> dev lifecycle <

17. Filipe Oliveira
performance <at> redis <dot> com
> step 0 <

18. Filipe Oliveira
performance <at> redis <dot> com
> measure it <

19. Filipe Oliveira
performance <at> redis <dot> com
> if you can’t measure <
you can’t improve it

20. Filipe Oliveira
performance <at> redis <dot> com
> describe state <

21. Filipe Oliveira
performance <at> redis <dot> com
> step 1 <

22. Filipe Oliveira
performance <at> redis <dot> com
> set clear goals <

23. Filipe Oliveira
performance <at> redis <dot> com
> dev lifecycle <
1 ) setting perf goals
● At 3.3 seconds page load time, conversion rate was 1.5%
● At 4.2 seconds page load time, conversion rate was less than 1%
● At 5.7+ seconds page load time, conversion rate was 0.6%

24. Filipe Oliveira
performance <at> redis <dot> com
> 75% users <
PLT < 3.5 secs

25. Filipe Oliveira
performance <at> redis <dot> com
> step 2 <

26. Filipe Oliveira
performance <at> redis <dot> com
> ongoing feedback <

27. Filipe Oliveira
performance <at> redis <dot> com

28. Filipe Oliveira
performance <at> redis <dot> com
CODE REVIEW
PREVIEW /
UNSTABLE
RELEASE
MANUAL
PERF
CHECK
PROD
ISSUE

29. Filipe Oliveira
performance <at> redis <dot> com
CODE REVIEW
PREVIEW /
UNSTABLE
RELEASE
MANUAL
PERF
CHECK
PROD
ISSUE
BUFFERING ISSUES!!
BUFFERING ISSUES!!

30. Filipe Oliveira
performance <at> redis <dot> com
> make it simple <

31. Filipe Oliveira
performance <at> redis <dot> com
> as soon as possible <

32. Filipe Oliveira
performance <at> redis <dot> com
CODE REVIEW
PREVIEW /
UNSTABLE
RELEASE
ZERO TOUCH
PERF CHECK
ZERO TOUCH
PERF CHECK
ZERO TOUCH
PERF CHECK

33. Filipe Oliveira
performance <at> redis <dot> com

34. Filipe Oliveira
performance <at> redis <dot> com

35. Filipe Oliveira
performance <at> redis <dot> com

36. Filipe Oliveira
performance <at> redis <dot> com
> how we’re doing it <

37. Filipe Oliveira
performance <at> redis <dot> com
> how we’re
actually
doing it

38. Filipe Oliveira
performance <at> redis <dot> com
> step 3 <

39. Filipe Oliveira
performance <at> redis <dot> com
continuous improvement
mindset

40. Filipe Oliveira
performance <at> redis <dot> com
Why?
- codecov 2020 State of Open Source Code Coverage Impact -

41. Filipe Oliveira
performance <at> redis <dot> com
How?
- summary dashboard for Redis Ltd Performance CI tracking -

42. Filipe Oliveira
performance <at> redis <dot> com
How?
- summary dashboard details for Redis Ltd Performance CI tracking -
> 200 Active steady stable VMs on peak > 100K benchmark runs in ~= 1.5 years

43. Filipe Oliveira
performance <at> redis <dot> com
by branch
scalability analysis
by version
How?

44. Filipe Oliveira
performance <at> redis <dot> com
How?

45. Filipe Oliveira
performance <at> redis <dot> com
> step 4 <

46. Filipe Oliveira
performance <at> redis <dot> com
> Mentoring and Guidance <

47. Filipe Oliveira
performance <at> redis <dot> com
> Avoid information silos <

48. Filipe Oliveira
performance <at> redis <dot> com
> explain the why’s <

49. Filipe Oliveira
performance <at> redis <dot> com
1. Full process Flame Graph + main thread Flame
Graph
2. perf report per dso
3. perf report per dso,sym (w/wout callgraph)
4. perf report per dso,sym,srcline (w/wout callgraph)
5. identical stacks collapsed
6. hotpatch callgraph
1
Our example?

50. Filipe Oliveira
performance <at> redis <dot> com
1. Full process Flame Graph + main thread Flame
Graph
2. perf report per dso
3. perf report per dso,sym (w/wout callgraph)
4. perf report per dso,sym,srcline (w/wout callgraph)
5. identical stacks collapsed
6. hotpatch callgraph
Our example?
2

51. Filipe Oliveira
performance <at> redis <dot> com
1. Full process Flame Graph + main thread Flame
Graph
2. perf report per dso
3. perf report per dso,sym (w/wout callgraph)
4. perf report per dso,sym,srcline (w/wout callgraph)
5. identical stacks collapsed
6. hotpatch callgraph
Our example?
3

52. Filipe Oliveira
performance <at> redis <dot> com
1. Full process Flame Graph + main thread Flame
Graph
2. perf report per dso
3. perf report per dso,sym (w/wout callgraph)
4. perf report per dso,sym,srcline (w/wout callgraph)
5. identical stacks collapsed
6. hotpatch callgraph
Our example? 4
6

53. Filipe Oliveira
performance <at> redis <dot> com
> gains? <

54. Filipe Oliveira
performance <at> redis <dot> com
improved Redis
performance by up to 4x![1]
[1] - https:/
/redis.com/blog/redis-intel-performance-testing/
https:/
/redis.com/blog/redis-7-geographic-commands/

55. Filipe Oliveira
performance <at> redis <dot> com
> predictable <

56. Filipe Oliveira
performance <at> redis <dot> com
> sustainable <

57. Filipe Oliveira
performance <at> redis <dot> com
> scalable <

58. Filipe Oliveira
performance <at> redis <dot> com
> stress free <

59. Filipe Oliveira
performance <at> redis <dot> com
> challenging <

60. Filipe Oliveira
performance <at> redis <dot> com
> cool
stuff to
check
Load Testing with k6 on CI/CD
On a Sample Java HTTP App that uses a Redis backend

61. Filipe Oliveira
performance <at> redis <dot> com
> cool
stuff to
check
Load Testing with k6 on CI/CD
On a Sample Java HTTP App that uses a Redis backend

62. Filipe Oliveira
performance <at> redis <dot> com
>
redis.com
● our blogs
● email: performance <at> redis <dot> com
● github orgs:
○ https://github.com/redis-performance
○ https://github.com/redis/redis-benchmarks-specification
● happy to connect:
○ https://www.linkedin.com/in/filipecosta90/
○ https://twitter.com/fcosta_oliveira
Follow up

63. Filipe Oliveira
performance <at> redis <dot> com
>
redis.com

64. performance <at> redis <dot> com
thank you!
questions?