Before learning about wrk, my understanding of performance testing had been limited to ab (Apache Benchmark). I had the impression that the functionality of ab was relatively simple, that is, simply pressure testing a given API and then seeing how much concurrency was there. So I learned about it, and then I saw that other people were interested in wrk, so I recorded something about wrk in the meantime.
Today, I want to try to reproduce a problem, the need to achieve an effect is to fill the CPU, creating a very high load, my first idea is to use stress, the results found that actually have not been able to play, can only play half (50%) to the top, so explore what the problem, by the way, for the record
Recently, when trying a project, I found that the business was not normal, and then I wanted to see what errors were output from the logs in the Docker Container, and then I actually did not see any logs, so I positioned them in passing and simply made a record.
Recently, I migrated some of the project's dependency management tools from dep to go module, and there are some cool places and some unpleasant places, so here's a brief introduction to some of my personal views and feelings about the migration process.
In one of my previous articles: Handling GRPC Go Connection Handshake Issues, I described a problem I encountered with I described a Go GRPC problem I encountered and how it was eventually solved, and finally left myself a pitfall: how the http2 connection was established. Here’s how to fill that hole.
The services in our group provide both GRPC and HTTP interfaces, and most of the HTTP interfaces are directly converted from GRPC via grpc-gateway. Here is a brief description of the root cause and the solution.
The power of the Linux command line is well known, but there are so many magic tools in Linux that it's really hard to learn them all at once, so if you don't know which one to start with, try awk first and you'll love it!
Recently I found that the traffic on the development machine was a bit abnormal, so I used the tool to locate the traffic problem, and here I will record the command I used.
I've been experimenting with some NoSQL databases, and this is a record of my Clickhouse operations, not much of value, just some memo commands. In fact, Clickhouse is similar to standard SQL, so you can get started with a little experimentation.