Tom

Thanks for replying! Here is what you asked for. zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379/Interactive: Connecting... zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379: BeginConnectAsync 1 unique nodes specified zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379: OnConnectedAsync init (State=Connecting) Allowing 1 endpoint(s) 00:00:03 to respond... Awaiting 1 available...

Ok I Have upgraded from 2.2.62 to the latest nuget 2.2.88. The connection time unfortunately is still long, about 1.4 seconds. Here is the new log Connect log:zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379,asyncTimeout=3000,connectTimeout=3000,abortConnect=False,connectRetry=1zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379/Interactive: Connecting...zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379: BeginConnectAsync1...

I'm still not seeing a version in the log. My packages in visual studio shows that I'm on that pre-release... not sure. I really appreciate your help! Connect log:Connecting (sync)...

I am going to try those things and also I noticed that Lambda just came out with .net 6 support(im using .net core) which claims improvements in JIT as well...

Some really interesting results when using a JIT setting in the project file! core CS#1 1328 CS#2 1339 Normal Start 2.5ms .net 6 CS#1 1328 CS#2 1270 Normal start 2.14...

Also as an aside, I went back to the latest stable stack exchange redis and the performance was similar for the cold starts FYI

2022-03-02T18:17:16.282Z d0f13617-781d-4229-8b5b-dffeb6a2c3a7 Connect log:Connecting (sync) on .NET 6.0.1 -- 18:17:15.9634: zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379,asyncTimeout=3000,connectTimeout=3000,abortConnect=False,connectRetry=1 18:17:15.9820: zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379/Interactive: Connecting... 18:17:16.0029: zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379: BeginConnectAsync 18:17:16.0227: 1 unique nodes specified (with tiebreaker) 18:17:16.0229: zir1ouzc69wq8b4x.qtlqwe.clustercfg.usw2.cache.amazonaws.com:6379: OnConnectedAsync init (State=Connecting) 18:17:16.0231:...

Note that in lambda each lambda sandbox has its own multiplexer handling one user at a time.

Really appreciate your help Nick. This line of investigation has lead to dramatic improvements for our app across the board. Thanks for the work you do here and your help...

Adding that line made the lambda act very strangely. Duration shot up to 3 seconds. Log section that shows the delay: 20:47:25.6846: Response from 10.2.191.128:6379/Interactive / PING: SimpleString: PONG --...