Skip to main content
These settings are available in system.settings and are autogenerated from source.

max_execution_speed

The maximum number of execution rows per second. Checked on every data block when timeout_before_checking_execution_speed expires. If the execution speed is high, the execution speed will be reduced.

max_execution_speed_bytes

The maximum number of execution bytes per second. Checked on every data block when timeout_before_checking_execution_speed expires. If the execution speed is high, the execution speed will be reduced.

max_execution_time

The maximum query execution time in seconds. If query runtime exceeds the specified number of seconds, the behavior will be determined by the ‘timeout_overflow_mode’, which by default is set to throw.
The timeout is checked and the query can stop only in designated places during data processing. It currently cannot stop during merging of aggregation states, nor during most of query analysis (establishing a connection to a remote replica is one place where it can), and the actual run time will be higher than the value of this setting.

max_execution_time_leaf

Similar semantically to max_execution_time but only applied on leaf nodes for distributed or remote queries. For example, if we want to limit the execution time on a leaf node to 10s but have no limit on the initial node, instead of having max_execution_time in the nested subquery settings:
We can use max_execution_time_leaf as the query settings: