3 ms·
I use http://loadimpact.com/ http://loadimpact.com/ The free version can give you an idea of how your server will handle a small spike, and the other versions
by jbhelms 15y ago
I use http://loadimpact.com/ http://loadimpact.com/
The free version can give you an idea of how your server will handle a small spike, and the other versions are per day so if you only need to test once or so a week as you finish a sprint then it wouldn't be a horrible cost.
- icebraining 15y agoIt's odd that they let you just test any website without proving its yours (by e.g. putting special file in the root or something). Can't unauthorized testing be considered a DoS attack?
- kowsik 15y agoI can only speak for http://blitz.io http://blitz.io. We generate an account-specific UUID which becomes a URL that you need to make available on your app (adding a route in ruby/node.js or uploading a txt file). Before each load test we check that your UUID is available on the app. Even if your UUID is leaked, this is not a problem, since it's unique to your account. Unless of course, your Google/Facebook account gets compromised. We currently, do not support password logins. It's either OAuth/FB Connect or SSO through our partners.