On Apr 10, 2:47 pm, Hussein Badakhchani <[email protected]> wrote: > happy to share the results once I have them. To date I have been accepting > the arguments of my colleges on this issue but I think carrying out an > objective test is probably the best way to settle the matter.
Definitely the right thing to do. > Well, probably, but I'm under a difficult time constraint and we consider > any solutions that require code alterations to be less preferential than > those that don't (coding and testing the changes will take longer than > configuring infrastructure and testing the stack). Makes sense, but code you fix in clients is code someone else will maintain for you forever. Custom things you do to your own environment remain your problem forever. > Let's see what the performance impact of SASL is. If it happens to be > acceptable I'll post my results and an RFC to the NGINEX Memcached module > maintainers. :) There's no performance impact of SASL after the initial auth. This is very important. If your decisions are based on how well initial connect performs, you're optimizing for something you shouldn't be doing very much at all. Even with a cheaper connect, it costs considerably more than just issuing a request on an existing connection.
