digitaldemocratic/stress-tests/requirements.txt

async-generator==1.10
attrs==22.2.0
certifi==2022.12.7
exceptiongroup==1.1.0
h11==0.14.0
idna==3.4
outcome==1.2.0
pip==22.3.1
PySocks==1.7.1
PyYAML==6.0
selenium==4.8.2
setuptools==67.0.0
sniffio==1.3.0
sortedcontainers==2.4.0
sqlite3==0.0.0
trio==0.22.0
trio-websocket==0.9.2
urllib3==1.26.14
wheel==0.38.4
wsproto==1.2.0
[stress-tests] Documentation + necessary files to perform testing By executing tests in this normalised fashion it is easier to compare results between different instances or different patch levels. Roughly speaking there are two kinds of tests: - VM tests: which summarise general performance of the instance, without taking DD into account - DD tests: which simulates many logins and interactions with DD, while recording the session as a user would pereceive it from a browser By using these we should be able to consistently compare and improve performance. The original dd-stress-test.tpl.jmx tests file was prepared by Teradisk with hardcoded instance, threadcount and duration values. Testing should now be performed with `vm-test.sh` and `dd-test.sh` respectively, and the template file should stay generic. 2023-02-27 19:38:41 +01:00			`async-generator==1.10`
			`attrs==22.2.0`
			`certifi==2022.12.7`
			`exceptiongroup==1.1.0`
			`h11==0.14.0`
			`idna==3.4`
			`outcome==1.2.0`
			`pip==22.3.1`
			`PySocks==1.7.1`
			`PyYAML==6.0`
			`selenium==4.8.2`
			`setuptools==67.0.0`
			`sniffio==1.3.0`
			`sortedcontainers==2.4.0`
			`sqlite3==0.0.0`
			`trio==0.22.0`
			`trio-websocket==0.9.2`
			`urllib3==1.26.14`
			`wheel==0.38.4`
			`wsproto==1.2.0`