2020-02-25 13:12:12 +00:00
|
|
|
<yandex>
|
|
|
|
|
<profiles>
|
|
|
|
|
<default>
|
|
|
|
|
<allow_introspection_functions>1</allow_introspection_functions>
|
|
|
|
|
<log_queries>1</log_queries>
|
2020-06-04 15:51:34 +00:00
|
|
|
<metrics_perf_events_enabled>1</metrics_perf_events_enabled>
|
2020-08-19 15:08:23 +00:00
|
|
|
<!--
|
|
|
|
|
If a test takes too long by mistake, the entire test task can
|
|
|
|
|
time out and the author won't get a proper message. Put some cap
|
|
|
|
|
on query execution time to prevent this. Test query run time is
|
|
|
|
|
limited to about 2 seconds, but this limit applies to all queries,
|
|
|
|
|
including fill/create and maintenance such as downloading trace
|
|
|
|
|
logs, so it must be generous enough. As a second line of defense,
|
|
|
|
|
we might also add time check to perf.py script.
|
|
|
|
|
-->
|
|
|
|
|
<max_execution_time>300</max_execution_time>
|
2020-10-19 14:39:52 +00:00
|
|
|
|
|
|
|
|
<!-- One NUMA node w/o hyperthreading -->
|
2020-11-09 16:14:05 +00:00
|
|
|
<max_threads>12</max_threads>
|
2020-02-25 13:12:12 +00:00
|
|
|
</default>
|
|
|
|
|
</profiles>
|
2021-03-03 10:42:44 +00:00
|
|
|
<users>
|
|
|
|
|
<default>
|
|
|
|
|
<access_management>1</access_management>
|
|
|
|
|
</default>
|
|
|
|
|
</users>
|
2020-02-25 13:12:12 +00:00
|
|
|
</yandex>
|
