[no subject]

ajaykemparaj · 2013-11-23T02:28:49+00:00

On Thursday, February 25, 2016 at 10:53 AM, Yichun Zhang (agentzh) wrote:...

[no subject]

ajaykemparaj

Hi,

i was going through this https://github.com/agentzh/redis2-nginx-module

"When used in conjunction with lua-nginx-module, it is recommended to use the lua-resty-redis library instead of this module though, because the former is much more flexible and memory-efficient."

Is there any benchmark between the redis2-nginx-module and the lua-resty-redis in terms of memory efficiency

How can we specify something like upstream redis_cluster using the connect from lua-resty -redis ( or should we have acustom lua code if an redis endpoint doesnt connect failover to next available redis server )

syntax: ok, err = red:connect(host, port, options_table?)

  upstream redis_cluster {
        server 127.0.0.1:6379;
        server 127.0.0.1:6380;
    }

    server {
        location /redis {
            redis2_next_upstream error timeout invalid_response;
            redis2_query get foo;
            redis2_pass redis_cluster;
        }
    }

Thanks,

Ajay K

agentzh

Hello!

On Fri, Nov 22, 2013 at 10:28 AM, Ajay k wrote:
>
> Is there any benchmark between the redis2-nginx-module and the
> lua-resty-redis in terms of memory efficiency
>

You're encouraged to do the benchmark yourself with your own data set
and queries. I don't have any concrete benchmark results off hand to
share.

According to the implementations, ngx.location.capture requires extra
memory buffers to *capture* the subrequest's response and the memory
buffers in Nginx subrequests will not be freed up until the end of the
main request, which both lead to (significantly) larger memory
footprint as compared to the very lightweight lua-resty-redis library
for nontrivial applications.

>
> How can we specify something like upstream redis_cluster  using the connect
> from lua-resty -redis ( or should we have acustom lua code if an redis
> endpoint doesnt connect failover to next available redis server )
>

Well, you cannot mix lua-resty-redis with the upstream {} blocks. You
need to do the failover and load-balancing yourself, all in Lua, which
also opens the door for more flexibility.

Best regards,
-agentzh

ajaykemparaj

Thanks agentzh

On Sat, Nov 23, 2013 at 12:59 AM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Fri, Nov 22, 2013 at 10:28 AM, Ajay k wrote:
>
> Is there any benchmark between the redis2-nginx-module and the
> lua-resty-redis in terms of memory efficiency
>

You're encouraged to do the benchmark yourself with your own data set
and queries. I don't have any concrete benchmark results off hand to
share.

According to the implementations, ngx.location.capture requires extra
memory buffers to *capture* the subrequest's response and the memory
buffers in Nginx subrequests will not be freed up until the end of the
main request, which both lead to (significantly) larger memory
footprint as compared to the very lightweight lua-resty-redis library
for nontrivial applications.

>
> How can we specify something like upstream redis_cluster using the connect
> from lua-resty -redis ( or should we have acustom lua code if an redis
> endpoint doesnt connect failover to next available redis server )
>

Well, you cannot mix lua-resty-redis with the upstream {} blocks. You
need to do the failover and load-balancing yourself, all in Lua, which
also opens the door for more flexibility.

Best regards,
-agentzh

.

Thanks,

Ajay K