top | item 31757069 (no title) ratherlongname | 3 years ago How does this compare to a traditional Postgres deployment in terms of performance? Time-to-response for queries, latency and so on. discuss order hn newest nikita|3 years ago For many workloads it’s on par. Few are slower. Pathological case, working set doesn’t fit in memory allotted to pg but fits in file system page cache. There is not page cache in neon thomasfromcdnjs|3 years ago I find this one a little hard to believe.Regardless, what are some of the trade offs this implementation makes? (aka the cons) load replies (1)
nikita|3 years ago For many workloads it’s on par. Few are slower. Pathological case, working set doesn’t fit in memory allotted to pg but fits in file system page cache. There is not page cache in neon thomasfromcdnjs|3 years ago I find this one a little hard to believe.Regardless, what are some of the trade offs this implementation makes? (aka the cons) load replies (1)
thomasfromcdnjs|3 years ago I find this one a little hard to believe.Regardless, what are some of the trade offs this implementation makes? (aka the cons) load replies (1)
nikita|3 years ago
thomasfromcdnjs|3 years ago
Regardless, what are some of the trade offs this implementation makes? (aka the cons)