Ruslan Suprun
Ruslan Suprun
@gusfcarvalho i'll try!
@MateSousa hi, feel free to do so, didn't start anything yet
Sure Here is set of `DD_*` env variables that we are using: ``` DD_AGENT_HOST: xxx DD_SERVICE: xxx DD_VERSION: xxx DD_ENV: xxx DD_LOGS_INJECTION: true DD_PROFILING_ENABLED: true DD_SERVICE_MAPPING: xxx DD_TRACE_ENABLED: true DD_TRACE_SAMPLE_RATE:...
It's happening when `DD_PROFILING_ENABLED` is `true`, when it's `false` CPU usage spikes not happening `DD_LOGS_INJECTION` value does not affect anything related to CPU usage
We've upgraded from `2.7.4` and issue was present there too So we've decided to upgrade to latest version to see if issue is still there
@sanchda so this new env variable should be added along with `DD_PROFILING_ENABLED=true` or replacing this env variable with `DD_PROFILING_EXPORT_LIBDD_ENABLED=true`?
@sanchda tried this, small improvements are in place, but still CPU usage on start is too high 😢 Disabled profiling for now
@sanchda sorry for a long response, will test it in few days and will return back with feedback
@sanchda hi I've tried enabling profiling with `DD_PROFILING_ENABLE_CODE_PROVENANCE=false` option but still no luck with decrease of CPU usage on start
We are running 2 services First one using gunicorn to run with 12 workers per container, workers amount is set by env variable Options for gunicorn: `gunicorn -b 0.0.0.0:8000 -t...