Dear Franck 1. Are you making your Jmeter scripts dynamic (important data like usernames or phone-number which might create locks in your SAP application/database)? Can you please share your Jmeter scripts?
2. As pointed out in the email-trail, SAP application might have some restrictions on concurrency? We might have to look at SAP configurations. Also perhaps your SAP database settings? 3. The connect-time is very less in your test whereas the load-time is astronomically high. This indicated network is not a problem. The problem lies in the SAP server/application/database. 4. Hope the hardware (CPU, Memory) you are running for your SAP is sufficient. This shouldn't become a bottleneck under load. Perhaps you can monitor your server usage using top or iotop on unix boxes. 5. Pls also share the amount of data transferred between Jmeter and SAP. You can find this in the results section of your Jmeter test. Cheers! Deepak "The greatness of a nation can be judged by the way its animals are treated - Mahatma Gandhi" +91 73500 12833 [email protected] Facebook: https://www.facebook.com/deicool LinkedIn: www.linkedin.com/in/deicool "Plant a Tree, Go Green" Make In India : http://www.makeinindia.com/home On Mon, Sep 13, 2021 at 10:17 PM Felix Schumacher < [email protected]> wrote: > > Am 13.09.21 um 17:36 schrieb Franck Cruz: > > > Hi Felix, > > The problem started to happen in the last 3 months, before all processes > were executed without this error "Response code:408" and the load was not > adjusted. > > Than take a look around your setup and find things, that changed three > months ago ;) I would have a look at the settings in your servers > connectors (especially the 60s timeout in your response). > > > At this point, if we lower the load considerably, we don't get errors. The > problem is that we need to test the system under load and with some stress. > > I would try out, which concurrency level is still going well and take that > number (might add one to it) to the admins and ask, if that number rings > something on them. (here you can even ask the DB administrators, if they > see some contention on their DB connections) > > > We need to get back to the initial load with all processes. > > I will reinforce with the SAP systems administration team to validate > server-side connections. > > +1 > > Can you show us the request and response with such a 408 error? > > Felix > > Thanks > > Franck > > > Felix Schumacher <[email protected]> escreveu no dia > sábado, 11/09/2021 à(s) 16:26: > >> >> Am 09.09.21 um 11:38 schrieb Franck Cruz: >> >> Hello guys, >> >> I'm running JMeter to generate load on access to the SAP webclient >> running some processes. >> >> Processes run correctly in the first few minutes but meanwhile "Response >> code:408" starts to appear. >> >> This error only happens when I have all processes running simultaneously, >> individually it doesn't occur. >> >> Have a look at your concurrent connections on the server side. Are you >> reaching your set limits on the servers/proxies/load balancers? Do you see >> any error/warning messages in the server logs? >> >> Are there any time limits set on those ends (like 60 s, which would match >> the numbers you see in your tests). >> >> Take care to not overload your systems with your test plans. Start small >> and increment your load, to get a feeling for the setup. >> >> Felix >> >> >> We've been in talks with SAP for several weeks now, but it's still not >> possible to identify the problem. >> >> Has something similar happened to you? Can you help identify the cause of >> the problem? >> >> [image: image.png] >> >> >> Thanks >> >> Best regards,, >> >> *Franck Cruz* >> >>
