diff options
| author | Sergey Vojtovich <svoj@mariadb.org> | 2017-12-12 22:53:38 +0400 |
|---|---|---|
| committer | Sergey Vojtovich <svoj@mariadb.org> | 2017-12-13 12:46:33 +0400 |
| commit | 159a6c2e608d04732cb678c7691345b9b1dc69b1 (patch) | |
| tree | 1e3f015f20b5b84e291ad134e3c8dbb16af31dfc /sql/event_scheduler.cc | |
| parent | 751e0f6b1ebeddb4faa3437daa399103bb212ac2 (diff) | |
| download | mariadb-git-159a6c2e608d04732cb678c7691345b9b1dc69b1.tar.gz | |
MDEV-14505 - Threads_running becomes scalability bottleneck
Instead of updating global counter, calculate Threads_running on the fly.
All threads having command != COM_SLEEP are included.
Behaviour changes:
Previously SHOW STATUS and SHOW GLOBAL STATUS returned the same values
representing global status. Now SHOW STATUS always returns 1 indicating that
current session has 1 thread running.
Previously only threads that were executing dispatch_command() or running events
were accounted by Threads_running. Now it is rough equivalent of
SELECT COUNT(*) FROM INFORMATION_SCHEMA.PROCESSLIST WHERE state!='Sleep'
Diffstat (limited to 'sql/event_scheduler.cc')
| -rw-r--r-- | sql/event_scheduler.cc | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/sql/event_scheduler.cc b/sql/event_scheduler.cc index 1572fedff49..d0a2405526a 100644 --- a/sql/event_scheduler.cc +++ b/sql/event_scheduler.cc @@ -297,7 +297,6 @@ Event_worker_thread::run(THD *thd, Event_queue_element_for_exec *event) DBUG_ENTER("Event_worker_thread::run"); DBUG_PRINT("info", ("Time is %u, THD: %p", (uint)my_time(0), thd)); - inc_thread_running(); if (res) goto end; @@ -326,7 +325,6 @@ end: event->name.str)); delete event; - dec_thread_running(); deinit_event_thread(thd); DBUG_VOID_RETURN; |