3 ms·
I cannot fathom how you arrived at that conclusion - there are so many systems that need to display the results of complex data queries where caching or precomp
by spinningarrow 3y ago
I cannot fathom how you arrived at that conclusion - there are so many systems that need to display the results of complex data queries where caching or precomputing the results does not make sense - waiting several seconds for results would be normal in those cases.
- felixgallo 3y agoI've been building backend systems for over 35 years across many industries.
- financltravsty 3y agoI will echo what the parent said: there’s no way your backend is taking seconds (fucking seconds) to return data unless there is something terribly wrong with your system. Complex queries should be optimized. The only time I have run into query issues is when: I was lazy, and didn’t want to optimize the query/schema/data layout and structures; the system was built by someone of questionable sanity and skillset; or the generated data is legitimately compute intensive, requiring lots of math i.e. more ops and cycles, but at that point it’s a report and the user can wait for it to gen (but in this case it is a lot of math that hasn’t taken advantage of parrallization). In the wild, I’ve mostly seen people having zero clue what they’re doing (this includes management, who are as culpable for not caring about perf).
- spinningarrow 3y agoChatGPT and many AI tools take several seconds to return responses. I’m not saying it should always or even most of the time be the case (quite the opposite - I’m with you and parent on that) but to say that there is no situation like that strikes me as pretty odd.
- financltravsty 3y agoThis was not always the case; and local models respond almost instantly. In ChatGPT's case, I'm assuming they're throttling responses to not hemorrhage money.