West Wind WebSurge
Performance Testing long running API endpoints
Gravatar is a globally recognized avatar based on your email address. Performance Testing long running API endpoints
  Ravi
  All
  May 7, 2022 @ 08:20am

Hello , We are using Websurge 2.0 for running performance testing on our API endpoints. There are a couple of endpoints where we have a long-running synchronous process (20-30 secs) which does a lot of database operations in the backend (including Update and Delete operations)

We would like to load test these endpoints to simulate a scenario where we will have maybe up to 50 users hitting this endpoint with different transaction ids and we do not want the same transaction id being called from different threads until the initial thread has completed (successfully, errored out).

Thanks, Ravi.

Gravatar is a globally recognized avatar based on your email address. re: Performance Testing long running API endpoints
  Rick Strahl
  Ravi
  May 7, 2022 @ 03:52pm

20-30 seconds for a Web Request? This seems like a terrible idea - I think you probably want to think about an asynchronous process that submits the request and has some way to check for completion then pick up the result - you really don't want to create blocking requests for 30 seconds.

Be that as it may - WebSurge Sessions process 1 request after the other and wait for completion of each in each sessions. You can then run multiple simultaneous requests (threads) that simulate simultaneous clients.

As to transaction ids - there's no way to really do this, unless you create an add in using .NET code. You can intercept requests as they are made and modify the request content before it's sent.

+++ Rick ---

© 1996-2022