5 ms·
Half-baked startup idea: because VPS performance is so dependent on the VPS's neighbors, create a service that spins up a bunch and then compares them on demand
by sjs382 9y ago
Half-baked startup idea: because VPS performance is so dependent on the VPS's neighbors, create a service that spins up a bunch and then compares them on demand. Keep the highest performing one. Charge your users to perform these tests.
- jtokoph 9y agoInteresting. Any ideas on how to monitor/respond to a new noisy neighbor? Ongoing monitoring to see if performance degrades? Can you filter out your own usage from the performance rating?
- anc84 9y agoFeature request #1: Don't test on machine we currently test on in a neighbor.
- NKCSS 9y agoYou mean the 'Netflix Model'? This is what they do all the time on AWS; when needed, spin up a bunch of VM's; test performance, drop the ones that perform worse and use the better ones.
- tuananh 9y agodo you have any source for this?
- joedicastro 9y agoI don't know, but as NKCSS says, you could do probably that in AWS and being a client like Netflix. But stressing instances regularly to test them to find a better one is something that you could probably do on your own, but as a service I have serious doubts if the providers would like that from a given scale. I'm not sure, but I don't think that would be something rare to have you account suspended. Perhaps, if you arrive a some type of agreement with them and their "business model" is compatible wit that, maybe. But, don't give me too much credit in this, I'm only speculating.
- regularfry 9y agoI can't see it being that much of a problem for the providers, as long as running short-term machines isn't already an issue. You always run the risk that the performance of the machine will degrade over time as the host fills up anyway.