-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Major performance issues with bytea performance #2240
Labels
Comments
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jun 18, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jun 18, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jun 18, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jun 19, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jun 19, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jun 20, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jul 3, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jul 3, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jul 3, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jul 3, 2020
regevbr
added a commit
to PruvoNet/node-postgres
that referenced
this issue
Jul 3, 2020
brianc
added a commit
that referenced
this issue
Jul 7, 2020
fix: major performance issues with bytea performance #2240
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I encountered the exact same issue as #1286 wheres a simple query to retrieve a 100mb bytea column from a one table, one row DB takes forever and causes the cpu to spike at 100%, rendering my node instance unresponsive.
After investigating, I think I found the cause in the
pg-protocol
packagenode-postgres/packages/pg-protocol/src/parser.ts
Lines 91 to 93 in ea6ac2a
Which suffers from the same thing as the original issue - too many allocations and buffer copies going around. I believe the fix introduced back then in brianc/node-packet-reader#3 should solve the problem here.
The text was updated successfully, but these errors were encountered: