Skip to content
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 degradation between versions 4.2.0 and 6 #1006

Closed
meelash opened this issue Nov 19, 2019 · 5 comments
Closed

Major performance degradation between versions 4.2.0 and 6 #1006

meelash opened this issue Nov 19, 2019 · 5 comments
Labels
Idle Waiting for more information for a while...

Comments

@meelash
Copy link

meelash commented Nov 19, 2019

Using the ms-sql library I noticed a major degradation in performance after they upgraded the tedious version from 4.2.0 in this commit: tediousjs/node-mssql@b635268

What I am seeing is that the same benchmark set of inserts to a database takes more than 4.5 times longer to run after that upgrade. (Some information about my performance test is available here: tediousjs/node-mssql#939)

I am attempting to isolate and reproduce this using just the tedious library. So far, I am seeing a performance hit of approximately the same scale using the benchmarks in tedious/benchmarks, so my guess would be that the issue is the same. I will continue to isolate the exact commit where the performance degrades.

EDIT: It doesn't appear the results I initially reported were related, I will continue investigating this and report back.

@IanChokS
Copy link
Member

Hi @meelash, can you try to run your performance script against version 5.0.3 and see if it has the same latency time?

@MichaelSun90
Copy link
Contributor

Hi @meelash, I also just try to run the tests against 4.2.0 and 6.6.2(lastest), and I do not see a huge difference between these two performance vise. There is a proximately average 3-4 ms difference between these two. Please share any new findings from your side. Thanks 🙇

@meelash
Copy link
Author

meelash commented Nov 21, 2019

I've definitively identified the commit causing the performance degradation as this one:
d949dd8

I am working now to reproduce in a benchmark test and will report back.

@IanChokS
Copy link
Member

hi @meelash, any progress? :)

@IanChokS IanChokS added the Idle Waiting for more information for a while... label Dec 13, 2019
@IanChokS
Copy link
Member

IanChokS commented Feb 5, 2020

Closing for now, re-open if issue still persists

@IanChokS IanChokS closed this as completed Feb 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Idle Waiting for more information for a while...
Projects
None yet
Development

No branches or pull requests

3 participants