Settings - Revision history

Carli at 22:34, 4 October 2025

2025-10-04T22:34:55Z

← Older revision		Revision as of 00:34, 5 October 2025
Line 7:		Line 7:
	* <code>"Backtrace"</code>: <code>true</code> or <code>false</code> whether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities.		* <code>"Backtrace"</code>: <code>true</code> or <code>false</code> whether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities.
	* <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs), 1 means only one-dimensional partitioning.		* <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs), 1 means only one-dimensional partitioning.
	* <code>"DefaultEngine"</code>: one of <code>"memory" "sloppy" "logging" "safe"</code> that defines which persistency level to choose if a CREATE TABLE statement is executed without the <code>ENGINE</code> parameter		* <code>"DefaultEngine"</code>: one of <code>"memory" "sloppy" "logging" "safe"</code> that defines which [[Persistency and Performance Guarantees\|persistency level]] to choose if a CREATE TABLE statement is executed without the <code>ENGINE</code> parameter
	* <code>"ShardSize"</code>: default 60000, defines the size of a shard. Rule of thumb is that no shard scan should last longer than 100ms. For servers and workstations, a shard size of 60,000 is recommended. On Raspberry Pi, you should tend to 10,000 in order to get good use of parallelism.		* <code>"ShardSize"</code>: default 60000, defines the size of a shard. Rule of thumb is that no shard scan should last longer than 100ms. For servers and workstations, a shard size of 60,000 is recommended. On Raspberry Pi, you should tend to 10,000 in order to get good use of parallelism.

Carli at 10:50, 20 May 2024

2024-05-20T10:50:00Z

← Older revision		Revision as of 12:50, 20 May 2024
Line 8:		Line 8:
	* <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs), 1 means only one-dimensional partitioning.		* <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs), 1 means only one-dimensional partitioning.
	* <code>"DefaultEngine"</code>: one of <code>"memory" "sloppy" "logging" "safe"</code> that defines which persistency level to choose if a CREATE TABLE statement is executed without the <code>ENGINE</code> parameter		* <code>"DefaultEngine"</code>: one of <code>"memory" "sloppy" "logging" "safe"</code> that defines which persistency level to choose if a CREATE TABLE statement is executed without the <code>ENGINE</code> parameter
			* <code>"ShardSize"</code>: default 60000, defines the size of a shard. Rule of thumb is that no shard scan should last longer than 100ms. For servers and workstations, a shard size of 60,000 is recommended. On Raspberry Pi, you should tend to 10,000 in order to get good use of parallelism.

Carli at 21:03, 17 May 2024

2024-05-17T21:03:18Z

← Older revision		Revision as of 23:03, 17 May 2024
Line 1:		Line 1:
	Settings are changed by:		Settings are changed by:
	(settings "key" "value")		(settings "key" "value")
			And read by:
			(settings "key")
	The following settings are available:		The following settings are available:

Carli: Created page with "Settings are changed by: (settings "key" "value") The following settings are available: * `"Backtrace"`: `true` or `false` whether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities. * `"PartitionMaxDimensions"`: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs),..."

2024-05-17T21:02:52Z

Created page with "Settings are changed by: (settings "key" "value") The following settings are available: * <code>"Backtrace"</code>: <code>true</code> or <code>false</code> whether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities. * <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs),..."

New page

Settings are changed by:
(settings "key" "value")
The following settings are available:

* <code>"Backtrace"</code>: <code>true</code> or <code>false</code> whether to print backtraces from Scheme. Using true decreases the performance by ~10% but gives you better debugging capabilities.
* <code>"PartitionMaxDimensions"</code>: number from 0 to 10 how many partitioning dimensions are allowed at max. 0 means, don't partition shards for values (use it to workaround bugs), 1 means only one-dimensional partitioning.
* <code>"DefaultEngine"</code>: one of <code>"memory" "sloppy" "logging" "safe"</code> that defines which persistency level to choose if a CREATE TABLE statement is executed without the <code>ENGINE</code> parameter