Conversation
|
Got a benchmark? |
|
I ran a micro-benchmark focused specifically on the result parsing phase, isolating it from network and I/O overhead. To avoid noise from TCP and libpq I/O, I mocked the
The mock generates a result set of 10,000 rows × 10 columns. Results (ops/sec):
That’s roughly a +16% improvement in this isolated scenario. I’m aware this is not an end-to-end benchmark and does not include network latency or query execution time, but the goal here was to validate that caching parsers removes repeated calls to see here |
|
ncie - this certainly doesn't look like it hurts anything. thanks! |
Adds a
_parsersarray to cache column parsers per column. Reduces repeated calls to_types.getTypeParser()for every row.