From 2a1c3a86b0f0cb5b5b9e1f73ffb96983ff6f4d4e Mon Sep 17 00:00:00 2001 From: Alexander Zobnin Date: Mon, 24 Jul 2017 20:37:27 +0300 Subject: [PATCH] docs: fix typo --- docs/sources/reference/direct-db-connection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/reference/direct-db-connection.md b/docs/sources/reference/direct-db-connection.md index 8ad1a09..71d9bb7 100644 --- a/docs/sources/reference/direct-db-connection.md +++ b/docs/sources/reference/direct-db-connection.md @@ -8,7 +8,7 @@ returns huge amount of data. In order to display it, plugin should adjust time s by using [consolidateBy](/reference/functions/#consolidateby) function. Ultimately, Grafana displays this reduced time series, but that data should be loaded and processed on the client side first. Direct DB Connection solves this two problems by moving consolidation to the server side. Thus, client get ready-to-use dataset which has much smaller -size. Data loads faster and client don't spend time for data processing. +size. Data loads faster and client doesn't spend time for data processing. Also, many users point better performance of direct database queries versus API calls. This caused by several reasons, such as additional PHP layer and additional SQL queries (user permissions checks).