News for hackers. Stuff that matters.
Re:March 20 ChatGPT outage: Here’s what happened by cplli on Friday March 24, 2023 @01:40PM (#35292728)
For caching the query results you get from your database. Also it's easier to spin up Redis and replicate it closer to your user than doing that with your main database. From my experience anyway.
Re:March 20 ChatGPT outage: Here’s what happened by mike_hearn on Friday March 24, 2023 @01:50PM (#35292927)
I think the idea is that if your db can hold the working set in RAM and you're using a good db + prepared queries, you can just let it absorb the full workload because the act of fetching the data from the db is nearly as cheap as fetching it from redis.
Re:March 20 ChatGPT outage: Here’s what happened by killerstorm on Friday March 24, 2023 @01:59PM (#35293073)
> For caching the query results you get from your database.

This only makes sense if queries are computationally intensive. If you're fetching a single row by index you aren't winning much (or anything).

Re:March 20 ChatGPT outage: Here’s what happened by dpkirchner on Friday March 24, 2023 @02:03PM (#35293136)
Of course? I'm not really sure what the original question actually is if you know that users benefit from caching the results of computationally intensive queries.
Re:March 20 ChatGPT outage: Here’s what happened by killerstorm on Friday March 24, 2023 @02:14PM (#35293303)
OpenAI uses redis to store pieces of text. Fetching pieces of text is not computationally intensive.
Re:March 20 ChatGPT outage: Here’s what happened by mannyv on Friday March 24, 2023 @04:35PM (#35295065)
Most likely they have them in an rdbms, so it's more like joining a forum thread together. Not expensive, but why not prebuild and store it instead?
Re:March 20 ChatGPT outage: Here’s what happened by acuozzo on Friday March 24, 2023 @05:38PM (#35295959)
> This only makes sense if queries are computationally intensive.

Or if the link to your DB is higher latency than you're comfortable with.