This repository has been archived by the owner on Apr 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Hints to overload protection and ANALYZE command #325
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -100,6 +100,20 @@ gets flushed after every operation. Setting this to ``ASYNC`` will improve | |
insert performance, but it also worsens durability. If a node crashes before a | ||
translog has been synced, those opperations will be lost. | ||
|
||
Overload Protection | ||
------------------- | ||
|
||
The `Overload Protection`_ settings control how many resources operations like | ||
amotl marked this conversation as resolved.
Show resolved
Hide resolved
|
||
``INSERT INTO FROM QUERY`` or ``COPY`` can use. | ||
|
||
The default values serve as a starting point for an algorithm that dynamically | ||
adapts the effective concurrency limit based on the round-trip time of requests. | ||
Whenever one of these settings is updated, the previously calculated effective | ||
concurrency is reset. | ||
|
||
Please update the settings accordingly, especially if you are benchmarking insert | ||
performance. | ||
|
||
Comment on lines
+103
to
+116
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
Refresh interval | ||
---------------- | ||
|
||
|
@@ -113,6 +127,20 @@ If you know that your client application can tollerate a higher refresh | |
interval, you can expect to see performance improvements if you increase this | ||
value. | ||
|
||
Calculating statistics | ||
---------------------- | ||
|
||
After loading larger amounts of data into new or existing tables, it is recommended | ||
to re-calculate the statistics by executing the ``ANALYZE`` command. | ||
The statistics will be used by the query optimizer to generate better execution plans. | ||
|
||
The calculation of statistics happens periodically. The bandwidth used for collecting statistics | ||
is limited by applying throttling based on the maximum amount of bytes per second that can | ||
be read from data nodes. | ||
|
||
Please refer to the `ANALYZE`_ documentation for further information how to change the | ||
calculation interval, and how to configure throttling settings. | ||
|
||
Manual optimizing | ||
----------------- | ||
|
||
|
@@ -132,9 +160,11 @@ even specific partitions) on your own schedule. If so, you can use the | |
.. _fulltext indexes: https://crate.io/docs/crate/reference/en/latest/sql/fulltext.html | ||
.. _natural primary key: https://en.wikipedia.org/wiki/Natural_key | ||
.. _OPTIMIZE: https://crate.io/docs/crate/reference/en/latest/sql/reference/optimize.html | ||
.. _ANALYZE: https://cratedb.com/docs/crate/reference/en/latest/sql/statements/analyze.html | ||
.. _refresh_interval: https://crate.io/docs/crate/reference/en/latest/sql/reference/create_table.html#refresh-interval | ||
.. _Solid-State Drives: https://en.wikipedia.org/wiki/Solid-state_drive | ||
.. _surrogate primary key: https://en.wikipedia.org/wiki/Surrogate_key | ||
.. _system column: https://crate.io/docs/crate/reference/en/latest/sql/administration/system_columns.html | ||
.. _translog.durability: https://crate.io/docs/crate/reference/en/latest/sql/reference/create_table.html#translog-durability | ||
.. _turning column indexes off: https://crate.io/docs/crate/reference/en/latest/sql/ddl/indices_full_search.html#disable-indexing | ||
.. _Overload Protection: https://cratedb.com/docs/crate/reference/en/latest/config/cluster.html#overload-protection |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JFYI: We usually sort those alphabetically, instead of just adding new links at the bottom.