The big with for Redis is pipelining IMO.
Big “win”
Redis is fast – I'll cache in Postgres
281–290 of 311 posts
Re: Redis is fast – I'll cache in Postgres
#282Earlier quoted context omitted.
What would a "proof" of that even look like? There are thousands (probably millions) of us walking around with anecdotal personal evidence at this point.
Some years ago when everybody here gave their anecdotal evidence about how Bitcoin and Blockchain were the future and they used it every day. You were a fool if you did not jump on the bandwagon. If the personal opinions on this site were true, half of the code in the world would be functional, lisp would be one of the languages most used and Microsoft would have not bougth DropBox. I really think HN hive minds opini…
I'm going to believe my own experience on this one.
Re: Redis is fast – I'll cache in Postgres
#283Earlier quoted context omitted.
It's crazy how wildly inaccurate "top-of-the-list" LLMs are for straightforward yet slightly nuanced inquiries. I've asked ChatGPT to summarize Go build constraints, especially in the context of CPU microarchitectures (e.g. mapping "amd64.v2" to GOARCH=amd64 GOAMD64=v2). It repeatedly smashed its head on GORISCV64, claiming all sorts of nonsense such as v1, v2; then G, IMAFD, Zicsr; only arriving at rva20u64 et al un…
How was the LLM accessing the docs? I’m not sure what the best pattern is for this. You can put the relevant docs in your prompt, add them to a workspace/project, deploy a docs-focused MCP server, or even fine-tune a model for a specific tool or ecosystem.
So, in short, do a lot of unrelated, complex, expert-level work, to get basic answers - all while I could just read the docs?
Where's that productivity increase everyone's been talking about?
Re: Redis is fast – I'll cache in Postgres
#284Earlier quoted context omitted.
Wait, what? Isn't that the whole point, to ask it specific tidbits of information? Are we to ask it large, generic pontifications and claim success when we get large, generic pontifications back? The narrative around these things changes weekly.
ChatGPT is exceptionally good at using search now, but that's new this year, as of o3 and then GPT-5. I didn't trust GPT-4o and earlier to use the search tool well enough to be useful. You can see if it's used search in the interface, which helps evaluate how likely it is to get the right answer.
The problem is, I ask it a basic question, it confidently feeds me bullshit, I correct it twice, and only then it does an actual search.
Re: Redis is fast – I'll cache in Postgres
#285Earlier quoted context omitted.
> copy pasting some configuration I might not really understand Uh, yea... why would you? Do you do that for configurations you found that weren't from LLMs? I didn't think so. I see takes like this all the time and I'm really just mind-boggled by it. There are more than just the "prompt it and use what it gives me" use cases with the LLMs. You don't have to be that rigid. They're incredible learning and teaching too…
My comment is mainly in opposition to the "five minutes" part from parent. If you have 5 minutes then you can't as you say : > Then I will dig deeper into those things myself ... So my point is I don't care if it's coming from LLM or a random blog, you won't have time to know if it's really working (ideally you would want to benchmark the change). If you can't invest the time better to stay with the defaults, which i…
Original commenter here. I don't disagree with your larger point. However, it turns out that the default settings for PostgreSQL have been super conservative for years; as a stable piece of infrastructure they seem to prefer defaulting to a constrained environment rather than making assumptions about resources. To their credit, PostgreSQL does ship with sample configs for "medium" and "large" deployments which are well-documented with comments and can be simply copied over the original default config.
I happen to have a good bit of experience with PostgreSQL, so that colored the "5 minutes" part of it. Still, most of the time, you "have" more than 5 minutes to create the orchestrator's deployment config for the service (which never exists by default on any k8s-based orchestrator). I'm simply saying to not be negligent of the service's own config, even though a default exists.
Re: Redis is fast – I'll cache in Postgres
#286Earlier quoted context omitted.
> for only about five minutes of LLM query or web search I think I have more trust in the PG defaults that in the output of a LLM or copy pasting some configuration I might not really understand ...
Then either have the LLM explain the config, or go Google it. LLM output is a starting point, not your final config.
Yes - as the original commenter, this was certainly my meaning (though I didn't spell it out).
Re: Redis is fast – I'll cache in Postgres
#287Earlier quoted context omitted.
Yes I do think not all people could fix it with Youtube. My grandma couldn't for example. I had a neigbor come for help with something like that too. Is not that hard to understan mate. Maybe put my comment in the LLM so you can get it. What is your point again?
My analogy holds up. Anyone could type "optimize my PostgreSQL database by editing the configuration file" into an LLM, but most people won't - same as most people won't watch YouTube to figure out how to unblock a sink. If you don't like the sink analogy what analogy would you use instead for this? I'm confident there's a "people could learn X from YouTube but chose to pay someone else instead" that's more effective…
You're exactly right (original commenter here). I began my career in professional software engineering in 1998. I've despaired that trained monkeys could probably wreck this part of the economy for over 25 years. But we're still here. :D
Re: Redis is fast – I'll cache in Postgres
#288> Both postgres and redis are used with the out of the box settings Ugh. I know this gives the illusion of fairness, but it's not how any self-respecting software engineer should approach benchmarks. You have hardware. Perhaps you have virtualized hardware. You tune to the hardware. There simply isn't another way, if you want to be taken seriously. Some will say that in a container-orchestrated environment, tuning go…
> Ugh. > if you want to be taken seriously For someone so enthusiastic about giving feedback you don't seem to have invested a lot of effort into figuring out how to give it effectively. Your done and demeanor diminish the value of your comment.
Thanks for the feedback. I'll definitely think about it.
Re: Redis is fast – I'll cache in Postgres
#289> Both postgres and redis are used with the out of the box settings Ugh. I know this gives the illusion of fairness, but it's not how any self-respecting software engineer should approach benchmarks. You have hardware. Perhaps you have virtualized hardware. You tune to the hardware. There simply isn't another way, if you want to be taken seriously. Some will say that in a container-orchestrated environment, tuning go…
> This is the kind of thing that is "hard and tedious" for only about five minutes of LLM query or web search time not even! if you don't need to go super deep with tablespace configs or advanced replication right away, pgtune will get you to a pretty good spot in the time it takes to fill out a form. https://pgtune.leopard.in.ua/ https://github.com/le0pard/pgtune
Glad you mentioned these resources. I was soft-pedaling it to avoid the "Look, a gatekeeper!" brigade.
Re: Redis is fast – I'll cache in Postgres
#290Earlier quoted context omitted.
ChatGPT is exceptionally good at using search now, but that's new this year, as of o3 and then GPT-5. I didn't trust GPT-4o and earlier to use the search tool well enough to be useful. You can see if it's used search in the interface, which helps evaluate how likely it is to get the right answer.
The problem is, I ask it a basic question, it confidently feeds me bullshit, I correct it twice, and only then it does an actual search.
I use GPT-5 thinking and say "use search" if I think there's any chance it will decide not to.