High memory usage about dd-trace-rb HOT 9 CLOSED

Thanks. I've uploaded logs for request #102561

from dd-trace-rb.

Thanks @DubHunt for reporting that! Performances (and memory usage) are critical and we'll investigate that one immediately. Can you open a ticket so that we can collect more details about your stack and how the tracer is instrumenting (or auto-instrumenting) your application?

Thank you a lot!

from dd-trace-rb.

Getting same issue. Similar graph. Removing ddtrace for now to see if it improves.

from dd-trace-rb.

@ponny thanks for reporting this! We've already found one possible cause where in some code paths Rails spans are not properly closed. As soon as the fix is in place and released, we contact you again. Thanks a lot for pointing out this critical issue!

from dd-trace-rb.

Hey @palazzem - Has there been any update on this? Thanks.

from dd-trace-rb.

Hi @mgodwin! We're working on it right now since it has the highest priority. At the moment, we're triaging Rails cases where a trace is not finished and flushed. Mostly, it should be related to code exceptions, or to our integration listeners that are not triggered by Rails. If this is the case, it's possible that the memory grows a lot in high traffic environments (it's not expected of course) because the tracing context holds an incomplete trace, that is not closed and removed from memory.

We'll keep you updated with this critical issues that is a huge stopper.

from dd-trace-rb.

We ran 0.8.2-RC1 on one of our servers for 3 days and the memory utilization looked similar to all of our other servers. 👍

from dd-trace-rb.

that's great! thanks @DubHunt for the follow-up! we need to address another connected issue today, but we'll ship the 0.8.2 tomorrow whatever!

Thanks everyone for your precious feedback! Will update the issue when the release is out.

from dd-trace-rb.

Cool, @DubHunt we've released a new version that has the fix: https://github.com/DataDog/dd-trace-rb/releases/tag/v0.8.2

I suggest everyone involved in this issue to try this new version if it's solved or not. /cc @mgodwin @ponny

from dd-trace-rb.