Gor
Hey
Gor | Hey | |
---|---|---|
7 | 38 | |
18,290 | 17,294 | |
- | - | |
4.8 | 0.0 | |
13 days ago | 11 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Gor
-
Launch HN: Codeparrot (YC W23) – Automated API testing using production traffic
I love to see more activity in this area!
I'm maintainer of GoReplay https://github.com/buger/goreplay and work in this area for the last 10 years.
It is quite hard problem to solve, because you have to deal with state difference between test and production environments. Love your approach to mocking dependencies, and leveraging OpenTelementry. It potentially can solve some of state issues. But still require modifying user code. I wonder if it can be done purely using OpenTelementry (e.g. you depend on typical OTel setup), and then read the data directly from OTel DB.
Cheers!
- A Golang-based open-source network monitoring tool
- Ask HN: How do you do Load Testing this 2022?
-
Axum launch system command then kill process
I put `top` command here so you can test my code but in production it will be something else (gor is your are interested). Just think of a process that doesn't end on its own (top,tail, etc.).
- GoReplay - test your system with real data
-
Ask HN: JMeter Alternative?
I suppose the end goal is to replicate production traffic patterns as close as possible. Why not just use production traffic? Of course omitting PII is mandatory.
Take a look at goreplay. https://github.com/buger/goreplay/wiki
-
How To Find Performance Issues Before Deploying
Not OP, but that is the idea. I use this tool for it, as it is dead-simple to get running and fairly configurable: https://github.com/buger/goreplay
Hey
-
AWS SnapStart - Part 19 Measuring cold starts and deployment time with Java 17 using different Lambda memory settings
The results of the experiment below were based on reproducing approximately 100 cold starts for the duration of our experiment which ran for approximately 1 hour. For it (and all experiments from my previous articles) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman
-
Data API for Amazon Aurora Serverless v2 with AWS SDK for Java - Part 5 Basic cold and warm starts measurements
The results of the experiment to retrieve the existing product from the database by its id see GetProductByIdViaAuroraServerlessV2DataApiHandler with Lambda function with 1024 MB memory setting were based on reproducing more than 100 cold and approximately 10.000 warm starts with experiment which ran for approximately 1 hour. For it (and experiments from my previous article) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman. We won't enable SnapStart on the Lambda function first.
-
AWS SnapStart - Part 15 Measuring cold and warm starts with Java 21 using different synchronous HTTP clients
The results of the experiment below were based on reproducing more than 100 cold and approximately 100.000 warm starts with experiment which ran for approximately 1 hour. For it (and experiments from my previous article) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman. I ran all these experiments for all 3 scenarios using 2 different compilation options in template.yaml each:
-
AWS SnapStart - Part 13 Measuring warm starts with Java 21 using different Lambda memory settings
In our experiment we'll re-use the application introduced in part 9 for this. There are basically 2 Lambda functions which both respond to the API Gateway requests and retrieve product by id received from the API Gateway from DynamoDB. One Lambda function GetProductByIdWithPureJava21Lambda can be used with and without SnapStart and the second one GetProductByIdWithPureJava21LambdaAndPriming uses SnapStart and DynamoDB request invocation priming. We'll measure cold and warm starts using the following memory settings in MBs : 256, 512, 768, 1024, 1536 and 2048. I also put the cold starts measured in the part 12 into the tables to see both cold and warm starts in one place. The results of the experiment below were based on reproducing more than 100 cold and approximately 100.000 warm starts for the duration of our experiment which ran for approximately 1 hour. Here is the code for the sample application. For it (and experiments from my previous article) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman. Abbreviation c is for the cold start and w is for the warm start.
-
Diagnósticos usando dotnet-monitor + prometheus + grafana
Por último, podemos executar os testes de carga usando hey.
-
Amazon DevOps Guru for the Serverless applications - Part 2 Setting up the Sample Application for the Anomaly Detection
For running our experiments to provoke anomalies we'll use the stress test tool. You can use the tool of your choice (like Gatling, JMeter, Fiddler or Artillery), I personally prefer to use the tool hey as it is easy to use and similar to curl. On Linux this tool can be installed by executing
- Threadpool no aspnet e problemas de performance
-
The Uncreative Software Engineer's Compendium to Testing
Hey: is a fast HTTP load testing tool used to test web applications and APIs. It provides a CLI (command-line interface) and supports concurrent requests.
-
The TCP receiver only ack the minimum bytes of MSS one by one
The client and server nodes are CentOS7.9/X86_64. If the HTTP POST requests were sent directly to the server with hey -c 1, there are about 0.2% of cases that may timeout. If the HTTP POST requests were sent through an NGINX proxy on the client node, there are about 20% of cases will timeout. I've confirmed that only one backend node has this problem. All other nodes are 100% succeeded even with higher throughput.
-
Benchmarking SQLite Performance in Go. Using Go's awesome built-in simple benchmarking tools to investigate SQLite database performance in a couple of different benchmarks, plus a comparison to Postgres.
64 concurrent requests isn't a lot. Modern web apps can typically handle much more than that (depending on what the request does, of course). Try it yourself with a load tester like https://github.com/rakyll/hey against a Go HTTP server, for example the one I've built in https://www.golang.dk/articles/go-and-sqlite-in-the-cloud
What are some alternatives?
joincap - Merge multiple pcap files together, gracefully.
Vegeta - HTTP load testing tool and library. It's over 9000!
ipe - An open source Pusher server implementation compatible with Pusher client libraries written in GO
k6 - A modern load testing tool, using Go and JavaScript - https://k6.io
Hugo - The world’s fastest framework for building websites.
siege - Siege is an http load tester and benchmarking utility
heka - DEPRECATED: Data collection and processing made easy.
anteon - Anteon (formerly Ddosify) - Effortless Kubernetes Monitoring and Performance Testing. Available on CLI, Self-Hosted, and Cloud
Postman - CLI tool for batch-sending email via any SMTP server.
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
syncthing - Open Source Continuous File Synchronization
kubernetes - Production-Grade Container Scheduling and Management