-
Notifications
You must be signed in to change notification settings - Fork 2
/
quarkus-activemq.hf.yaml
169 lines (169 loc) · 7.38 KB
/
quarkus-activemq.hf.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
# This is the name of the benchmark. It's recommended to keep this in sync with
# name of this file, adding extension `.hf.yaml`.
name: quarkus-activemq
# We must define at least one HTTP target, in this case it becomes a default
# for all HTTP requests.
http:
- host: http://localhost:8080
sharedConnections: 4000
- host: http://localhost:8081
sharedConnections: 4000
phases:
- rampup:
increasingRate:
initialUsersPerSec: 1
targetUsersPerSec: 4000
# We expect at most 1000 users being active at one moment - see below
maxSessions: 4000
duration: 6m
forks:
createFork:
weight: 1
scenario:
# The only sequence in this scenario is called `test`.
- createLegumesScenario:
# Step `randomItem` randomly picks one item from the list below...
- randomInt: itemId <- 1 .. 99999
- randomUUID: itemDescription
- httpRequest:
# HTTP request will read the variable from the session and format
# the path for the GET request
POST: /legumes/
authority: localhost:8080
headers:
content-type: application/json
body: |
{
"description":"Shows up on summer - ${itemDescription}",
"name":"Courgette-${itemId}"
}
handler:
# We'll check that the response was successful (status 200-299)
status:
range: 2xx
# When the response is fully processed we'll set variable `completed`
# in the session.
onCompletion:
set: completed <- yes
# For demonstration purposes we will set `sync: false`.
# Next step is executed immediately after we fire the request, not
# waiting for the response.
# sync: false
gettersFork:
weight: 3
scenario:
- getLegumesScenario:
- randomInt: pageIndex <- 1 .. 99
- httpRequest:
GET: /legumes?pageIndex=${pageIndex}
authority: localhost:8080
handler:
# We'll check that the response was successful (status 200-299)
status:
range: 2xx
# When the response is fully processed we'll set variable `completed`
# in the session.
onCompletion:
set: completed <- yes
# For demonstration purposes we will set `sync: false`.
# Next step is executed immediately after we fire the request, not
# waiting for the response.
# sync: false
- awaitVar: completed
- getHeroesScenario:
- randomInt: pageIndex <- 1 .. 9
- httpRequest:
GET: /heroes?pageIndex=${pageIndex}
authority: localhost:8081
handler:
# We'll check that the response was successful (status 200-299)
status:
range: 2xx
# When the response is fully processed we'll set variable `completed`
# in the session.
onCompletion:
set: completed <- yes
# For demonstration purposes we will set `sync: false`.
# Next step is executed immediately after we fire the request, not
# waiting for the response.
# sync: false
- awaitVar: completed
- mainPhase:
constantRate:
# users will be starting the scenario every second
usersPerSec: 4000
duration: 6m
startAfter: rampup
forks:
createFork:
weight: 1
scenario:
# The only sequence in this scenario is called `test`.
- createLegumesScenario:
# Step `randomItem` randomly picks one item from the list below...
- randomInt: itemId <- 1 .. 99999
- randomUUID: itemDescription
- httpRequest:
# HTTP request will read the variable from the session and format
# the path for the GET request
POST: /legumes/
authority: localhost:8080
headers:
content-type: application/json
body: |
{
"description":"Shows up on summer - ${itemDescription}",
"name":"Courgette-${itemId}"
}
handler:
# We'll check that the response was successful (status 200-299)
status:
range: 2xx
# When the response is fully processed we'll set variable `completed`
# in the session.
onCompletion:
set: completed <- yes
# For demonstration purposes we will set `sync: false`.
# Next step is executed immediately after we fire the request, not
# waiting for the response.
# sync: false
# We'll wait for the `completed` var to be set in this step, though.
gettersFork:
weight: 3
scenario:
- getLegumesScenario:
- randomInt: pageIndex <- 1 .. 99
- httpRequest:
GET: /legumes?pageIndex=${pageIndex}
authority: localhost:8080
handler:
# We'll check that the response was successful (status 200-299)
status:
range: 2xx
# When the response is fully processed we'll set variable `completed`
# in the session.
onCompletion:
set: completed <- yes
# For demonstration purposes we will set `sync: false`.
# Next step is executed immediately after we fire the request, not
# waiting for the response.
# sync: false
- awaitVar: completed
- getHeroesScenario:
- randomInt: pageIndex <- 1 .. 99
- httpRequest:
GET: /heroes?pageIndex=${pageIndex}
authority: localhost:8081
handler:
# We'll check that the response was successful (status 200-299)
status:
range: 2xx
# When the response is fully processed we'll set variable `completed`
# in the session.
onCompletion:
set: completed <- yes
# For demonstration purposes we will set `sync: false`.
# Next step is executed immediately after we fire the request, not
# waiting for the response.
# sync: false
- awaitVar: completed