REDIS INFO at regular intervals

[Rama Rao]

We are running redis INFO command for every 2 sec to get the statistics. Is this too frequent? Does it have any performance impact in a production redis with high concurrent requets?

Thanks,

[Salvatore Sanfilippo]

Should not be a problem, INFO takes more or less 30 usec to run.
However if you want to reduce this even further, you may use the "INFO
section" form if you are only interested in certain things.

For instance "INFO" can be ran 40,000 times per second, while "INFO
monitor" can be ran 120,000 times per second.

Cheers,
Salvatore

> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to redis-db+u...@googlegroups.com.
> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at https://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.



--
Salvatore 'antirez' Sanfilippo
open source developer - Redis Labs https://redislabs.com

"If a system is to have conceptual integrity, someone must control the
concepts."
— Fred Brooks, "The Mythical Man-Month", 1975.

[Rama Rao]

OK. Cool. Thanks.

Cheers,

Rama

On Mon, Jun 12, 2017 at 8:59 PM, Salvatore Sanfilippo <ant...@gmail.com> wrote:

Should not be a problem, INFO takes more or less 30 usec to run.
However if you want to reduce this even further, you may use the "INFO
section" form if you are only interested in certain things.

For instance "INFO" can be ran 40,000 times per second, while "INFO
monitor" can be ran 120,000 times per second.

Cheers,
Salvatore

On Mon, Jun 12, 2017 at 5:21 PM, Rama Rao <ramarao...@gmail.com> wrote:
> We are running redis INFO command for every 2 sec to get the statistics. Is
> this too frequent? Does it have any performance impact in a production redis
> with high concurrent requets?
>
> Thanks,
>

> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to redis-db+unsubscribe@googlegroups.com.

> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at https://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.

--
Salvatore 'antirez' Sanfilippo
open source developer - Redis Labs https://redislabs.com

"If a system is to have conceptual integrity, someone must control the
concepts."
       — Fred Brooks, "The Mythical Man-Month", 1975.

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.

To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe@googlegroups.com.

[Joshua Scott]

For what it's worth, we have found that INFO takes much longer when there are thousands of clients connected (on the order of 1ms or so). We haven't seen that calling INFO every 15 sec or so has a measurable impact on performance, though.

Josh Scott

[Salvatore Sanfilippo]

Thanks Joshua, that makes sense, it is due to the statistics section
that attempts to provide the longest output buffer. Probably it should
be removed from INFO... or at least the tracking should be performed
incrementally and INFO should just report the cached information
rather than computing it on the fly.

> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to redis-db+u...@googlegroups.com.

[Rama Rao]

Makes sense. Probably getting from cache makes this lot predictable

On Wed, Jun 21, 2017 at 3:02 AM, Salvatore Sanfilippo <ant...@gmail.com> wrote:

Thanks Joshua, that makes sense, it is due to the statistics section
that attempts to provide the longest output buffer. Probably it should
be removed from INFO... or at least the tracking should be performed
incrementally and INFO should just report the cached information
rather than computing it on the fly.

On Tue, Jun 20, 2017 at 9:39 PM, Joshua Scott <joshua...@gmail.com> wrote:
> For what it's worth, we have found that INFO takes much longer when there
> are thousands of clients connected (on the order of 1ms or so). We haven't
> seen that calling INFO every 15 sec or so has a measurable impact on
> performance, though.
>
> Josh Scott
>
>
> On Monday, June 12, 2017 at 10:21:53 AM UTC-5, Rama Rao wrote:
>>
>> We are running redis INFO command for every 2 sec to get the statistics.
>> Is this too frequent? Does it have any performance impact in a production
>> redis with high concurrent requets?
>>
>> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to redis-db+unsubscribe@googlegroups.com.

> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at https://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.

--
Salvatore 'antirez' Sanfilippo
open source developer - Redis Labs https://redislabs.com

"If a system is to have conceptual integrity, someone must control the
concepts."
       — Fred Brooks, "The Mythical Man-Month", 1975.

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.

To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe@googlegroups.com.