mistral/mistral/scheduler
Renat Akhmerov 511be4f98f Initialize profiler for scheduler threads
* It turns out that osprofiler wasn't initialized properly for
  threads in which scheduler runs its jobs. So profiling simply
  didn't work for this threads and lots of important info didn't
  get to the profiler log. This patch fixes it.
* When evaluating a YAQL expression, sometimes we get a huge result
  value that we always put into the debug log. In practice, it doesn't
  make much sense and, moreover, it utilizes lots of CPU and disk
  space. It's better shrink it to some reasonable size that would
  allow to make necessary analysis, if needed.
* Other minor style fixes according to the Mistral coding guidelines.

Change-Id: I3df3ab96342c456429e20a905615b90bcb94818d
2020-01-30 16:23:56 +07:00
..
__init__.py New experimental scheduler: the first working version 2018-08-14 14:02:19 +07:00
base.py Improve new scheduler 2019-08-16 13:39:39 +07:00
default_scheduler.py Initialize profiler for scheduler threads 2020-01-30 16:23:56 +07:00
scheduler_server.py New experimental scheduler: the first working version 2018-08-14 14:02:19 +07:00