Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
Description
We need to benchmark how much slowdown we experience when we add the optimizer trace to the
server.
We would need the comparision for:
1) server without the optimizer trace (current 10.4)
2) server with optimizer trace disabled here. (currently in branch 10.4-mdev6111)
The optimizer trace is currently disabled by default.
Please run sysbench.
Attachments
Issue Links
- is part of
-
MDEV-6111 optimizer trace
-
- Closed
-
- relates to
-
MDEV-18822 investigate performance regressions in 10.4
-
- Stalled
-
Take-aways from discussion with svoj: Profiling with `perf top -p $MYSQLD_PID` shows this:
0,27% mysqld [.] Json_writer_object::Json_writer_object
0,23% mysqld [.] Json_writer_object::~Json_writer_object
0,17% mysqld [.] Json_writer_object::add
0,08% mysqld [.] Json_writer_object::add_table_name
0,07% mysqld [.] Json_writer_object::Json_writer_object
0,05% mysqld [.] Json_writer_object::add
extra load adds up to 0.87%
some time later:
0,25% mysqld [.] Json_writer_object::~Json_writer_object
0,25% mysqld [.] Json_writer_object::Json_writer_object
0,22% mysqld [.] Json_writer_array::Json_writer_array
0,17% mysqld [.] Json_writer_object::add
0,12% mysqld [.] Json_writer_array::~Json_writer_array
0,09% mysqld [.] Json_writer_object::add_table_name
0,07% mysqld [.] Json_writer_object::add
0,06% mysqld [.] Json_writer_object::Json_writer_object
1.23% in total.
the worlkoad is same as above, sysbench oltp_point_select.lua, 1 thread, 1 table, 100000 records