3 ms·
That is actually on its way also. We're going to offer a "single test" option, where a user gets to use the system for an hour. But maybe we should make it 24 h
by rlonn 18y ago
That is actually on its way also. We're going to offer a "single test" option, where a user gets to use the system for an hour. But maybe we should make it 24 hours instead?
- agotterer 18y agoMaybe charge a similar way to how you are doing monthly... 1-5 tests are X dollars 5-20 tests X more dollars. A single test is only useful if you want know what your system can physically handle. If you are trying to tweak settings to get the most optimal configuration, multiple tests will obviously be needed. Can you handle very large sites? I assume your system is in the cloud and scales as needed?
- rlonn 18y agoWe don't want to make the different subscription offers too complicated, which is why we've stayed away from having people pay per number of tests executed, or similar. I agree that people will want to tweak and run several tests, but a 1-day subscription sounds pretty reasonable then, I think, no? We currently simulate max 5,000 concurrent users on a site and that is something our own servers can handle, so right now we're not using cloud services. We do have support for running the backend on a cloud though - we've been testing it and it works very well. If customers start asking about running larger tests, then we will probably implement a cloud backend mode that will feature a much, much larger traffic-generating capability (but also be more expensive).
- agotterer 18y agoI think a 1 day subscription makes sense. But from your own usage standpoint, theres a significant difference between running 1 or 2 tests and running 100 in a day. 5,000 seems like a good start. I'm looking for bigger :) Good luck!