It can be used to simulate a heavy load on a server, group
of servers, network or object to test its strength or to
analyze overall performance under different load types.
https://jmeter.apache.org/
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
No content
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
No content
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
WEB SERVER access & error logs
DB size, throughput, slow queries
CACHE size, hits vs. misses, connections
SYSTEM cpu & mem usage, disk i/o
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
No content
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
WHAT TO LOOK FOR?
reading from & writing to disk
network calls & latency
database queries
CPU & memory usage
Slide 57
Slide 57 text
WHAT TO DO
TO IMPROVE
APP PERFORMANCE?
Slide 58
Slide 58 text
WRITING EFFICIENT CODE
single vs. double quotes
\count() vs. count()
avoid regexes
tabs instead of spaces
Slide 59
Slide 59 text
WRITING EFFICIENT CODE
single vs. double quotes
\count() vs. count()
avoid regexes
tabs instead of spaces
Slide 60
Slide 60 text
MICRO-OPTIMIZATIONS
RARELY ARE THE ISSUE
focus on data
often there are huge gains around:
API-Requests, DB-Queries,
Slide 61
Slide 61 text
MICRO-OPTIMIZATIONS
RARELY ARE THE ISSUE
automate micro-optimizations,
if you want, but focus on
measured bottlenecks (see tools)