-
Notifications
You must be signed in to change notification settings - Fork 82
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
Slow reports after upgrading to v2.13.2 #975
Comments
Hi @cdmwebs, thank you for reporting this! If you think it could be related to these large SQL In between the two versions of our Elixir integration that you upgraded from, we changed how I see that you also mention that you think it might be related to #971. Do you have a theory as to why? Does your application use check-ins, or fetch data using Hackney? |
That does seem relevant, @unflxw. I forgot about the NIF. We'll get a query over to you soon. Thanks for the quick response. |
Yes, setting |
Hi @cdmwebs @codingbull, AppSignal for Elixir 2.13.3 has been released, with a fix to the issue above. 🎉 Please let us know if you run into any problems with it. |
Can confirm that 2.13.3 has addressed this slowness. Thanks! |
Describe the bug
We're still working to narrow down the actual issue, but after upgrading our app from v2.13.0 to v2.13.2, one of our async tasks that previously took ~3 seconds ballooned to ~3 minutes. The SQL body of the
insert
statements are fairly large.We tested our docker image, application server, database connection, VPC timing, and finally disabled Appsignal to try to figure out where the issue was. We noticed an immediate improvement with Appsignal disabled.
We upgraded to 2.13.2 on 11/25, which is roughly the same time the issue appears in our samples. We then downgraded our staging and production servers to 2.13.0 and (so far) performance has returned to prior levels.
Still trying to see if we can provide additional info but wanted to open this to get the ball rolling. It could possibly be related to #971.
To Reproduce
Steps to reproduce the behavior:
TBD
The text was updated successfully, but these errors were encountered: