Open fpietrosanti opened 11 years ago
Testing over Tor2web has been done with: ab -c 1000 -n 50000 -f DHE-RSA-AES256-SHA https://65.112.221.20/antanistaticmap/decoy.html
Testing over NGINX has been done with: ab -c 1000 -n 50000 -f DHE-RSA-AES256-SHA https://globaleaks.org/
The testing against nginx didn't missed a single SSL connection. The testing against Tor2web missed 5-10% of SSL connection with "Failed handshake" .
We should also investigate "why" some connection fail the SSL handshake.
@fpietrosanti is this still an issue? I am interested in investigating if so.
time passe by and i remember that things were for me failing the same on globaleaks.org or google.com
ab -c 1000 -n 50000 -f DHE-RSA-AES256-SHA https://www.google.com/
Following scalability improvement as #94, during stress-testing it has been verified that Tor2web is extremely slow under excessive load.
Below AB testing with 1000/s connections:
Percentage of the requests served within a certain time (ms) 50% 31156 66% 35975 75% 40326 80% 43149 90% 49321 95% 54200 98% 62341 99% 66119 100% 82693 (longest request)
This means that Tor2web is not behaving properly under excessive load, basically self-dossing itself.
This maybe a performance issue to be tuned by removing some still present performance issue.
The same test, done over https://globaleaks.org/ that run a nginx platform with 1/3 of the hardware resources within the respect of Tor2web testing machine, give better responsive result: Percentage of the requests served within a certain time (ms) 50% 9915 66% 10276 75% 11883 80% 13082 90% 13250 95% 18880 98% 19080 99% 19095
We should investigate: a) Which a request to serve a local file is going to take between 30-45 seconds b) How can detect this overload condition and act over it