3 ms·
> I'm not sure why it just needs to be taken as a given that databases will take 150ms to return any data. Run your database on a t2.small instance on AWS (1 v
by tpxl 4y ago
> I'm not sure why it just needs to be taken as a given that databases will take 150ms to return any data.
Run your database on a t2.small instance on AWS (1 vCPU, 2GiB RAM). Why would you do that, you ask? I don't know, but that's what we got on an old job.
This was also used to prove MongoDB is faster than PostgreSQL, even though Mongo was running on-prem on much better hardware.
- supermatt 4y agoNope, single digit millisecond performance for me on those nodes when the tables are cached - anything else and you are complaining about performance of the storage medium.
- tpxl 4y agoHow much data? We were doing a few million writes/day on peak days and the nodes couldn't keep up.
- supermatt 4y agoA few million writes a day is still well within the write performance of one of those nodes. But... we were talking about querying the data, no?
- tpxl 4y agoWell yes, but if your database is busy writing, it's going to have less time for reading.
- deleted 4y ago[deleted]
- supermatt 4y agoI'm not sure what your point is. You said the nodes are slow. They are not slow, and will handle thousands of requests a second when configured correctly. If you arent getting that then you are doing something big, something inefficient, or something stupid - and that would be the same on any size node. Size your instances accordingly.