[#714] decrease number of requests to grafana and increase cpu #729
Conversation
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
mcdoker18
requested review from
kirillmakhonin,
botsman and
alexander-semenets
|
bot, test all |
|
Can one of the admins verify this patch? |
1 similar comment
|
Can one of the admins verify this patch? |
|
Build status: FAILURE |
|
bot, test all |
|
Build status: FAILURE |
By default grafana uses the sqlite database. Many concurrent connections can be issue. For example, deletion of a dashboard response 404 status code, when the dashboard presents.
mcdoker18
force-pushed
the
feat/714-dashboard-not-exist
branch
from
40c5f89 to
7160699
Compare
|
bot, test all |
|
Build status: SUCCESS |
botsman
approved these changes
Jan 15, 2019
kirillmakhonin
approved these changes
Jan 16, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By default grafana uses the sqlite database. Many concurrent
connections can be issue. For example, deletion of a dashboard response
404 status code, when the dashboard presents.
PR fixes this comment #714 (comment)