{"id":11116,"date":"2024-04-17T15:17:46","date_gmt":"2024-04-17T19:17:46","guid":{"rendered":"https:\/\/www.redline13.com\/blog\/?p=11116"},"modified":"2024-04-17T15:20:02","modified_gmt":"2024-04-17T19:20:02","slug":"ramping-vus-in-k6","status":"publish","type":"post","link":"https:\/\/www.redline13.com\/blog\/2024\/04\/ramping-vus-in-k6\/","title":{"rendered":"Ramping VUs in k6"},"content":{"rendered":"

<\/a> \"Ramping<\/p>\n

When creating a load test, it is sometimes desirable to control how the rate of requests are scaled over time. k6<\/a> provides this behavior through the ramping-vus<\/strong><\/a><\/code> executor, which allows gradual scaling of virtual users over a specified duration. This enables realistic simulations of user traffic patterns as expected in real-world use cases. In this brief post, we will outline the basics of using this feature in k6.<\/p>\n

<\/a>Example Script of Ramping VUs<\/h3>\n

The following k6 script outlines the syntax and usage of the\u00a0ramping-vus<\/code><\/strong>\u00a0executor. You can also find a similar script example in the official k6 documentation pages<\/a>:<\/p>\n

import http from 'k6\/http';\n<\/strong>import { sleep } from 'k6';\n\n<\/strong>export const options = {\n<\/strong>  discardResponseBodies: true,\n<\/strong>  scenarios: {\n<\/strong>    contacts: {\n<\/strong>      executor: 'ramping-vus',\n<\/strong>      startVUs: 0,\n<\/strong>      stages: [\n<\/strong>        { duration: '300s', target: 100 },\n<\/strong>        { duration: '60s', target: 0 },\n<\/strong>      ],\n<\/strong>      gracefulRampDown: '30s',\n<\/strong>    },\n<\/strong>  },\n<\/strong>};\n\n<\/strong>export default function () {\n<\/strong>  http.get('https:\/\/test.k6.io\/contacts.php');\n<\/strong>  sleep(0.5);\n<\/strong>}<\/strong><\/pre>\n
In this two-stage example, the parameters specified tell k6 to first gradually ramp up users from zero to 100 simultaneous VUs over 5 minutes (i.e.<\/em>, 300 seconds). From that point, VUs are gradually taken out of rotation to smoothly taper back down to zero over the next 60 seconds. Finally, there is a graceful ramp down period specified of 30 seconds, which gives this additional time for requests to complete without abruptly ending the process.<\/p>\n
<\/a>Ramping VUs Configuration Options<\/h3>\n
In the above example, there are three options specific to the\u00a0ramping-vus<\/code><\/strong> executor. These are:<\/p>\n