node-continuation-local-storage
node-continuation-local-storage copied to clipboard
Stored value missing in large concurrent hit
Hi, We tried using continuation-local-storage in a loopback application. The value was set at the entry point (server.js) and inside the api-method, we just checked if we receive the same text being set while entry is received. While running j-meter with 500 requests in a span of one second, we got it fine. But, while running (500 requests / second * 100) it went unmatched.
Observing the same issue in my application. Under heavy load , the same value is used for multiple requests.