2 ms·
Looks great. My only thinking is how I would interpret the pricing. It is $0.003 per second. So if a single test took 10 seconds, it would cost £0.03. It doesn
by martin-adams 8y ago
Looks great. My only thinking is how I would interpret the pricing.
It is $0.003 per second. So if a single test took 10 seconds, it would cost £0.03. It doesn't say if that's per second per test, or per second of parallel usage.
If for example, I have 250 tests each taking an average of 10 seconds. Is that 2,500 seconds - $7.50 per test suite run. If not, surely I can't run 250 tests in parallel for a total of 10 seconds.
- kevlened 8y agoI see how that could be confusing; I'll add clarity around pricing. Currently it mirrors the way serverless computing is priced - per second of compute time per instance. So, your second example is correct. I started with $0.003 per second, because it aligns with existing cloud-hosted grids. An example pricing model is ~$200/month for 2 parallel instances with 1000 min. Assuming unlimited parallelism, you get $0.00333 per second. 20+ parallel browsers on existing services are at least a couple thousand every month. I don't think remote grids are the best solution for every test performance problem, and for some test loads, local runs can be faster. That said, pricing weighs into the remote vs local decision, so I really appreciate the feedback.