Check resource limits (max open files) for local scenarios #54

New issue

Closed

opened 2023-04-21 10:59:53 +00:00 by ale64bit · 0 comments

ale64bit commented

2023-04-21 10:59:53 +00:00

Member

When running scenarios backed by local storage engine, the user running the scenario (and thus the engine) is often not the same as the service user. As a result, the resource limits (in particular, the max number of open files) of the user running the scenario apply. This is problematic as most tests need to open a large number of files and the default soft limits are often too restrictive (e.g. 1024).

Describe the solution you'd like

Check the resource limits before creating the local engine and fail if they are too low.

Additional context

https://k6.io/docs/misc/fine-tuning-os/
https://github.com/golang/go/issues/46279

## Is your feature request related to a problem? Please describe. When running scenarios backed by local storage engine, the user running the scenario (and thus the engine) is often not the same as the service user. As a result, the resource limits (in particular, the max number of open files) of the user running the scenario apply. This is problematic as most tests need to open a large number of files and the default soft limits are often too restrictive (e.g. 1024). ## Describe the solution you'd like Check the resource limits before creating the local engine and fail if they are too low. ## Additional context https://k6.io/docs/misc/fine-tuning-os/ https://github.com/golang/go/issues/46279