tracer: set tracing compiled in by default#44684
Conversation
|
@ideepika could you please take a look at the |
40015fd to
d22d2a6
Compare
Yeah, there are some updates that we'd need to set Jaeger as always on, I will update them |
c10bcfe to
04f4ba2
Compare
fcaf6ca to
2973230
Compare
2973230 to
b6fe24f
Compare
|
jenkins test api |
4a1799c to
573d0cf
Compare
|
PR description was updated. added commits relevant for enabled tracing. |
specify --without-jaeger during rpm build process if jaeger package install is not desired. Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
jaeger opentelemetry deps that will be installed by default now: libyaml-dev > 0.6 libthrift-dev (thift deps: libevent-dev, bison, flex, boost(we use ceph compiled boost)) nlohmann-json3-dev removes: pkg.ceph.jaeger build package optional option Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
flag Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
the batch span processor holds batch of spans until timeout reached or it fills up, instead of sending each span alone which is a huge overhead Signed-off-by: Omri Zeneva <ozeneva@redhat.com>
since we are using batch span processor, the tracer does not send the spans by himself. so a single tracer is good enough. Signed-off-by: Omri Zeneva <ozeneva@redhat.com>
Signed-off-by: Omri Zeneva <ozeneva@redhat.com>
Signed-off-by: Omri Zeneva <ozeneva@redhat.com>
f651103 to
dd57ad6
Compare
It probably wouldn't be a bad idea so we don't end up having to do a backtrace later in case this ends up being a bigger loss than we expected. Was @benhanokh able to help run the tests on a faster setup? |
@ideepika can you please re-review? (PR is currently blocked on this request) |
@markhpc @yuvalif @mattbenjamin @ideepika randread randwrite those are the IOPS of the tests. |
|
jenkins retest this please |
|
jenkins test make check |
|
jenkins test make check |
|
nice work @zenomri! and thanks to everyone else that helped! |
|
@zenomri Great job and thank you much for the performance work! |
@ideepika @zenomri how was the change in |
Following performance testing on tracing code, this PR sets WITH_JAEGER=ON by default, and performance optimization was done in order to minimize tracing overhead when tracing is compiled in and disabled, which is the base state of tracing.
NoopTracer->StartSpan(...).in addition, changes were done in order to optimize performance when tracing is enabled:
here are the latest hsbench results:
UPDATED 15 Feb
WITH_JAEGER=OFF- linkWITH_JAEGER=ON, tracing disabled - linkWITH_JAEGER=ON, tracing enabled - linkthere is no effect on performance when tracing is disabled.
when tracing is enabled, we are having degradation of ~18% on PUT operations, and ~10% on GET operations.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume tox