i can record the simulation through Gatling and able to run the simulation, but i am getting less load time compared to actual UI (User Interface) when generating the reports.
In my case actual load time when i click on some button(one request,it internally loads some data) on UI is almost 3 to 4 mins, but in reports it will show 300 ms...
i can clicked the button then it will take 2 to 4 minutes after that it open one excel, this during time not coming the reports, the reports giving time 300 or 360 ms.
the button url placed script in scala and run again but it gives wrong loading time(360 ms)
Thanks in advance,
any suggestions are helpful to me.
Related
my website receives a lot of data through websockets, as I display data in real time. (I would say like 30 objects/second). It works well, but after some time (I don't know exactly how much, but like 30 min ~ 1 hour) I get the error "Aw, snap".
What I think is causing the error is that I have a table where whenever I receive one specific type of object, I add it into the table. I receive at least 15 objects every second and it loads some text but also image. I think it is giving the error because of the images.
Is there anything I can do to avoid this error? Because I really need the data and the images too. But I do not want the page crashing after some time..
I'm new to Nextjs. I have implemented a page. The SSR is used. But as you can see in the picture, there are a lot of workboxes running, each lasting 100 to 300 milliseconds, and this has increased the load time.
I see your problem. You are loading all the Image and Product Components at once, so the entire website is lagging. You have to split the search, maybe 10 to 15 products per viewport, and when user scrolls through the end, load the next 10 to 15 products and so on.
you can use useEffect with useState to do so.
Also, adjust the API to fetch limited data at times,
i.e:
https://api.com/getproducts?quantity=10
I am using angular-moment library. Essentially, I want to show the time difference in minutes between now and some time in the model. Ideally, the display must be dynamic; so the user doesn't need to refresh the page in order to see updates.
<span am-time-ago="message.time"></span> works and works dynamically. But it shows user-friendly messages "a few seconds ago, 2 minutes ago, etc. I need the actual value in minutes (30 means in 30 minutes, -120 means I am 2 hours late, etc.)
Everything else, for example moment(myJsonValue).diff(moment(), 'minutes') is not dynamic. Is there a way to have both dynamic and numeric?
I am using Angular-datatables for tabular pagination of JSON data. My JSON data is of 1000 records and it takes time to load. I want to load only 100 records at the very first time and when I click on 'Next' button, the next 100 records should gets loaded. I am new in Angular please help me and guide.
Okay that might reduce the time taken to load your files but on the contrary it makes you send 100 requests to the server which is not good.
When dealing with huge data you cannot expect much speed. But, You can optimize the ng-repeat performance by using
Track by
BindOnce
Infinite Scroll
These things will improve the performance to an extent.
Apologies if this request is similar to others - I am new to JMeter and have searched for other relevants posts but couldn't find anything - or maybe I just didn't understand them!
I'm performance testing a system with a web based application. The front end system will be processing records submitted into the system via MQ - the front end allows the user to pick up a record from the queue, validate some detail, make changes and submit the changes.
There will be 20 users using the front end to do this message validation, update and submission.
Each user is expected to need 30 seconds to pick a message from queue, make changes and resubmit - so we are expecting 1 user to process 120 records/hour, so 20 users will be expected to process 2400 records/hour
The picking up the record off the queue, changing it and submitting the changes will be done via 3 individual web pages.
SO - think time across the 3 pages has been defined as 24 seconds (leaving 6 of the 30 second limit for rendering, server responses, db calls etc.)
However I don't know how to specify this within JMeter. From my reading I can see that I can add a Timer in as a parent to a sampler and I assume I can add a Timer in as a parent of the Recording Controller? - but I need to be able to specify that the 24 second think time is spread across those 3 different pages.
I read a post elsewhere suggesting that if I record using the proxy after adding the Gaussian Random Timer in as a child of the Test Plan (parent to everything else) then the http proxy will record the think time as a ${T} variable in the Gaussian Random Timer - I tried this and this didn't work (also I don't want to rely on this - I'd like to be able to understand and make changes to think time properly rather than relying on JMETER to do it for me.)
To reiterate - 20 users, 30 seconds for 1 user to complete a transaction, TT defined as 24 seconds - I am struggling what Timer to use, where to put it so that the think-time is spread across the samplers that equate to the GETS associated with the 3 pages the user will navigate through.
Apologies for the lengthy post - I just wanted to be clear and concise.
Many thanks in advance,
As per JMeter Timers documentation
Note that timers are processed before each sampler in the scope in which they are found; if there are several timers in the same scope, all the timers will be processed before each sampler.
Timers are only processed in conjunction with a sampler. A timer which is not in the same scope as a sampler will not be processed at all.
To apply a timer to a single sampler, add the timer as a child element of the sampler. The timer will be applied before the sampler is executed. To apply a timer after a sampler, either add it to the next sampler, or add it as the child of a Test Action Sampler.
Now regarding "what timer to use"
There are 2 scenarios:
Virtual-User-oriented scenario - when you try to simulate N users working together
Goal-Oriented-scenario - when you try to produce N hits per second load.
In case of scenario 1 even Constant Timer can be quite enough, besides it will provide repeatability of results. See above quote for information on where to put your timer(s)
In case of scenario 2 you'll need Constant Throughput Timer. If 20 users process 2400 records per hour and each record assumes 3 web page calls, it means that 7200 requests will be made in one hour which in its turn stands for 120 requests per minute (this is what you should enter into the timer's "throughput" area) or 2 requests per second.