Reduce even more

Author: ardatan

.github/workflows/federation-v1.workflow.yaml

@@ -40,7 +40,7 @@ jobs:
     with:
       gateway: ${{ matrix.directory }}
       vu: 300
-      time: ${{ github.event_name == 'pull_request' && '30s' || '240s' }}
+      time: ${{ github.event_name == 'pull_request' && '30s' || '90s' }}
       baseDir: federation-v1
       scenarioDir: constant-vus-over-time
       scenarioName: constant-vus-over-time
@@ -80,7 +80,7 @@ jobs:
     with:
       gateway: ${{ matrix.directory }}
       vu: 300
-      time: ${{ github.event_name == 'pull_request' && '30s' || '240s' }}
+      time: ${{ github.event_name == 'pull_request' && '30s' || '90s' }}
       baseDir: federation-v1
       scenarioDir: constant-vus-over-time
       scenarioName: constant-vus-subgraphs-delay
@@ -121,7 +121,7 @@ jobs:
     with:
       gateway: ${{ matrix.directory }}
       vu: 500
-      time: ${{ github.event_name == 'pull_request' && '30s' || '240s' }}
+      time: ${{ github.event_name == 'pull_request' && '30s' || '90s' }}
       baseDir: federation-v1
       scenarioDir: constant-vus-over-time
       scenarioName: constant-vus-subgraphs-delay-resources
@@ -162,7 +162,7 @@ jobs:
     with:
       gateway: ${{ matrix.directory }}
       vu: 2000
-      time: ${{ github.event_name == 'pull_request' && '60s' || '240s' }}
+      time: ${{ github.event_name == 'pull_request' && '60s' || '90s' }}
       baseDir: federation-v1
       scenarioDir: ramping-vus
       scenarioName: ramping-vus

federation-v1/scenarios/constant-vus-over-time/README.md

@@ -4,7 +4,7 @@
 This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. It's being executed with a constant amount of VUs over a fixed amount of time. It measure things like memory usage, CPU usage, average RPS. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
 
 
-This scenario was running 300 VUs over 240s
+This scenario was running 300 VUs over 90s
 
 
 ### Comparison

federation-v1/scenarios/constant-vus-subgraphs-delay-resources/README.md

@@ -4,7 +4,7 @@
 This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. It's being executed with a constant amount of VUs over a fixed amount of time. It measure things like memory usage, CPU usage, average RPS. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
 
 
-This scenario was running 500 VUs over 240s
+This scenario was running 500 VUs over 90s
 
 
 ### Comparison

federation-v1/scenarios/constant-vus-subgraphs-delay/README.md

@@ -4,7 +4,7 @@
 This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. It's being executed with a constant amount of VUs over a fixed amount of time. It measure things like memory usage, CPU usage, average RPS. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
 
 
-This scenario was running 300 VUs over 240s
+This scenario was running 300 VUs over 90s
 
 
 ### Comparison

federation-v1/scenarios/k6.shared.js

@@ -79,7 +79,6 @@ const graphqlRequest = {
       "Content-Type": "application/json",
     },
   },
-  timeout: '240s',
 };
 
 export function handleBenchmarkSummary(data, additionalContext = {}) {

federation-v1/scenarios/ramping-vus/README.md

@@ -4,7 +4,7 @@
 This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. We are running a heavy load of concurrent VUs to measure response time and other stats, during stress. It measure things like memory usage, CPU usage, response times. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
 
 
-This scenario was trying to reach 2000 concurrent VUs over 240s
+This scenario was trying to reach 2000 concurrent VUs over 90s
 
 
 ### Comparison