ghz VS insomnia

I once built a quick and dirty load testing tool for a public facing service we built. The tool was pretty simple - something like https://github.com/bojand/ghz but with traffic and data patterns closer to what we expected to see in the real world. We used argo-workflows to generate scale.

One thing which we noticed was that there was a considerable difference in performance characteristics based on how we parallelized the load testing tool (multiple threads, multiple processes, multiple kubernetes pods, pods forced to be distributed across nodes).

I think that when you run non-distrubuted load tests you benefit from bunch of cool things which happen with http2 and Linux (multiplexing, resource sharing etc) which might make applications seem much faster than they would be in the real world.

I'm not sure. Maybe you can write to the discussion section of the repo https://github.com/bojand/ghz/discussions

In part 1 we looked at ghz for load testing gRPC services, and now I want to cover k6, which claims to be a modern load testing tool built for developer happiness. After only a brief experience with it I can see why is that and why Grafana moved to acquire k6 earlier this year.

It should be unbound, in this particular benchmark we set ghz concurrency to 50 and connections to 5 and we don't set the rps flag of ghz (e.g. --rps=2000, from this tool)

a second container running ghz makes unary requests to the server

Use tools like Postman or Insomnia to test the API endpoints and ensure they behave as expected.

We will be performing all of the authentication requests manually, however for testing purposes, you might want to use an API testing tool such as Postman or Insomnia.

For a very long time, the go-to tool was curl. Great, always available command line tool. Unfortunately, there is one small issue. It’s hard to keep requests and collect them in collections, it’s great for one-time shots or debugging, but for constant working with API could be painful. To solve it, I started working with tools like Postman/Insomnia. Then eh... strange licensing model, or changes which occurred from Kong side click, definitely push me again for some lookup. After checking different very popular tools and those not such well known I decided to use… Ansible. Sounds strange right? Let me explain this decision. For example, look at this code.

At first, I used Postman for testing APIs because it had a lot of features. But I switched to Insomnia because it was easier to use and kept everything organized. The big problem with Insomnia was that it deleted all my saved work when it made me create an account to keep using it.

Often used for cases where a project exposes a REST or other type of API service. Open API is a popular method of documenting such API services. It can also be used along side tools such as Swagger Codegen to produce boilerplate code for API interaction / testing purposes. There may also be support files for popular API testing tools such as Postman or Insomnia. This makes it easier at a glance to see what data is coming back from a call so the user knows how to handle parsing the data.

Well, there is this website that I have been trying to scrape for a few days now. I had tried everything from scrapy splash on docker to almost giving up because I read somewhere that it was JavaScript rendered. Since the source code from the inspect part of the developer tools was different from the source code from the view-source:https//... on the same developer tools.How could this be possible? Then I kept searching on internet and found this concept; where you can mimic web-browsers requests from a server using an API program,and it worked magically. Some of the API programs are postman and insomnia. I prefer using insomnia for this particular case , feel free to use any other API program of your choice.