I have executed my script for 1Vuser. For a particular request, NeoLoad is showing 23Sec but when I checked on Browser's console, it is just showing 3Sec.
There is very large gap in the response time.
When I was checking from Browser's console, I have cleared Browser's cache and it was the same machine through which I have executed the NeoLoad Script.
I have checked that particular request on multiple machines after that, it is taking around 3 sec only.
What can be the reason of it, and how to fix it?
I would assume there is a correlation issue with the script?
This particular request is coming during Login.
And after Login, we are creating some data through script which is getting created successfully.
So, I think there is no correlation issue.
Also, I have attached the screenshot of captured parameters and let me know if any other details are required.
--Authentication token has been handled.
Hi, there is nothing that can be done without much more detail, what is the request? we would need screenshots of the header and request from Neoload in order to guess the issue
What does the token look like, original vs the token.col1?
This is the Authorization token which looks like
Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImppYk5ia0ZTU2JteFBZck45Q0ZxUms0SzRndyIsImtpZCI6ImppYk5ia0ZTU2JteFBZck45Q0ZxUms0SzRndyJ9.eyJhdWQiOiI5YmZlZmI5ZS1lNjI5LTQzOTAtYTEzZi04NmE1NTBiZDhiNjIiLCJpc3MiOiJodHRwczovL3N0cy53aW5kb3dzLm5ldC8yZDcxY2M1NC1iYzllLTQ1MTgtYWViYy02MThjNmFhNjNmOWEvIiwiaWF0IjoxNjAxNDU5MDg2LCJuYmYiOjE2MDE0NTkwODYsImV4cCI6MTYwMTQ2Mjk4NiwiYWlvIjoiRTJSZ1lPQVNiZGt0Y09uSzR1YkVIazhUa3pKWEx6K2poNnNXYmhLNjNMbHY4WmFhang4QiIsImFtciI6WyJwd2QiLCJ3aWEiXSwiZW1haWwiOiJWYW5pdGEuS29obGlAYmhzcGVjaWFsdHkuY29tIiwiZmFtaWx5X25hbWUiOiJLb2hsaSIsImdpdmVuX25hbWUiOiJWYW5pdGEiLCJpcGFkZHIiOiIxMi4xNDguMTYwLjEzMCIsIm5hbWUiOiJLb2hsaSwgVmFuaXRhIChYY2VlZGFuY2UpIiwibm9uY2UiOiJiMGNiNzBkOS1lMjM3LTRhOTItYjFiOC0yZWQ1MDAzNmRhNjEiLCJvaWQiOiJhMDBlODgxYS0yZmRlLTRiMjEtYmQ3Zi0yZGYxMTZiZjM4OGMiLCJvbnByZW1fc2lkIjoiUy0xLTUtMjEtMzg4MjExODIyMC0yODkzNDg0NDM1LTI3OTM2MDAxMzItMjU0NjIiLCJyaCI6IjAuQUFBQVZNeHhMWjY4R0VXdXZHR01hcVlfbXA3N19wc3A1cEJEb1QtR3BWQzlpMkp1QVBZLiIsInN1YiI6IjJrbnZKcXRrYVctQThLeXB6U1lFRUdCYWdGeFdEUzJPenZqVVBRMThJczgiLCJ0aWQiOiIyZDcxY2M1NC1iYzllLTQ1MTgtYWViYy02MThjNmFhNjNmOWEiLCJ1bmlxdWVfbmFtZSI6IlZhbml0YS5Lb2hsaUBiaHNwZWNpYWx0eS5jb20iLCJ1cG4iOiJWYW5pdGEuS29obGlAYmhzcGVjaWFsdHkuY29tIiwidXRpIjoib18wWWNmQVM4RWFRdjBsWlctVVNBUSIsInZlciI6IjEuMCJ9.T36rerYTO_O6S5AjPM__ZaB1vPdN-ih2jctgguKk0BPOzPmj3oNnXsst0Zpim9sAClfENKdxkXyswviDS4GqQU5ITbxWcaYclHEqTtfVgzxkop8Vb7GYvGaIUD19W0jw5SygYiVOmrUvRP4hH41JShtc__rQjrf6grqY7nIvfK0nD90CtSgqGZ_8R_DkzyHaLZfXlNCZtACj2Bre9fa8DFhl8055xHCQcHbuUKVO2fsbCmJjwuWbeonr3qKoblRWaEZEai-a8bm1aebXA95pBb6nFvRa28PwMeyopX5TaKG1N9-OqV-qYy5kfkalReJ0qiOeHFXdE-ggfpnp2gGzqw
And, it is valid for 2hours, I have just created a variable to pass the valid token.
I have tried to extract it from previous request as well and its giving the same result.
So your variable "token.col1" includes the text Bearer, okay
I thought it would look like Bearer ${token.col1}
Getting the value from the previous response is a better option as it will always be valid, I would try to request from different LGs to see if it's a routing issue
Can you please explain how to do it from different LGs?
When you do a Check User Path, you are using the embedded Load Generator inside the Neoload GUI, running on your machine. My suggestion was to install a second Load Generator on another machine on a different part of the Network and run the Check from there. Assuming the test is fine, the only reason for the slower response might be the route taken from your machine to the server, that said, if the browsers dev tools is also on you machine it points back to the script. You need to work out if it's the test or environment
