Hi Kit,
Thanks for the suggestion, I don’t think we will reach that point at all, since
in the forward proxy, the header check will only function in the “CONNECT”
method, after that TLS handshake and encrypted traffic will be blind for
forward proxy.
it's sort of connection management instead
It is quite hard to judge since i think it is an apple-to-orange comparision.
but if you are accessing a local redis, then luasocket should be ok.
Thanks.
On Thu, Dec 22, 2016 at 10:18 AM, Di Li wrote:
> Sincerely apology on this.
>
> The bottleneck is on the webdis, which is a http front end of
Sincerely apology on this.
The bottleneck is on the webdis, which is a http front end of redis, since
ts.fetch only support http request, and pretty redis doesn’t support http
protocol
I changed the fetch url to something else, which is back to 12000 req/s.And I
did check the internal request,
One thing I can think of is that you may be calling ts.fetch()
unconditionally. We need to check if it is an internal request first.
If it is, it is likely done to the ts.fetch() and therefore we should
not do a ts.fetch() for an incoming internal request.
Otherwise it will result in a recursive s
Can you share your lua script in full with me?
Thanks.
Kit
On Thu, Dec 22, 2016 at 1:30 AM, Di Li wrote:
> Hey Guys,
>
> Running 6.2.0 with cherry pick of TS-4497 to make the ts.fetch work,
> otherwise it won’t even function.
>
> The performance came back with very terrible results, not sure t
