How we spent $30k in Firebase in less than 72 hours

Re:How we spent $30k in Firebase in less than 72 hours by diziet on Wednesday August 01, 2018 @11:20PM (#17669032)

It's only 460k QPS, with 16k documents everything would be cached really well. Or a single instance of redis can serve that load of reads fairly easily.

[ Parent | on HN ]

Re:How we spent $30k in Firebase in less than 72 hours by Xorlev on Thursday August 02, 2018 @12:21AM (#17669212)

Good luck with that. A single Redis would not be able to serve that workload. Maybe a single machine but you're really pushing the limits there just with concurrent TCP connections.

At that qps Redis has 2 microseconds per request.

I agree it caches well but your proposed architecture is definitely not production quality.

[ Parent | on HN ]

Re:How we spent $30k in Firebase in less than 72 hours by gcbirzan on Thursday August 02, 2018 @09:12AM (#17671128)

There is a difference between queries and connections. With pipelining, a redis machine can easily serve that. If they stored things in a better structure, like a list, they'd easily be able to get that.

On my machine 5 concurrent requests, at 100 items, it can do ~6 500 000 items per second, at 300, 11 000 000 per second, and it kind of caps out at that. Even with 1 concurrent connection, at 600 items, you get 6M per second.

[ Parent | on HN ]