Swoole
autocannon
Swoole | autocannon | |
---|---|---|
34 | 14 | |
18,229 | 7,599 | |
0.2% | - | |
8.6 | 6.5 | |
5 days ago | 9 days ago | |
C++ | JavaScript | |
Apache License 2.0 | MIT License |
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.
Swoole
-
Performance benchmark of PHP runtimes
Swoole
-
Go with PHP (why it's still a good idea to use PHP in 2023)
It's a management UI where concerns were raised that it downloads from third party server. However this issue was handled very fast and code was removed: https://github.com/swoole/swoole-src/issues/4434
-
PHP Swoole or OpenSwoole?
The contribution log of the original swoole seems to be active: https://github.com/swoole/swoole-src/graphs/contributors
-
5 PHP Frameworks You've (Probably) Never Heard of
FOMO is created by Iranian developer amirfaramarzi. This framework sits on top of the asynchronous event driven framework swoole that creates insane levels of performance out of apps (we're talking Go/Rust level of performance)! Check out the performance on the Web Frameworks Benchmark.
-
Why is Apache clinging to OpenOffice's corpse?
> I tend to install FOSS because imo they are more "future-proof", but some of them are developed by companies (e.g., Fedora Linux) and that makes me wonder if they're truly future-proof.
The story of CentOS should be telling that, no, many pieces of software that are backed by a company will not be future-proof and will probably experience certain changes as a consequence of that, be it being transformed to better fit corporate goals (CentOS Stream), or being retired eventually so the company may focus on something else (Atom), or will just be left to slowly rot over time as happens with most code (OpenOffice).
Then again, it's not like open source projects are that future proof or safe from "drama" either - for example, the Lubuntu project has 2 homepages for no reason: the official one at https://lubuntu.me/ and some other one that serves old versions and is not trusted by my ad blocking solution https://lubuntu.net/
There are also cases, when open source projects experience fragmentation like happened with Gogs https://gogs.io/ and Gitea https://gitea.io/en-us/ and sometimes there are cases where particular individuals simply cannot work together and as a consequence pretty much the same happens, as was the case with Swoole and Open Swoole: https://github.com/swoole/swoole-src/issues/4434
Treat most pieces of software that you use as if they might not be there in a year.
-
A Self-Hosted and Open-Source Alternative to Google’s Firebase Releases Version 0.14
It's known by devs, it's simple, it's getting updates... I like PHP. Sure it has downsides but what doesn't. Oh, and with Swoole, even performance is bumped.
-
Take your Serverless Functions to new speeds with Appwrite 0.13
To allow for synchronous execution and prioritize speed, we decided to depart from the task-based system that most of our workers use and instead create a new component to Appwrite called the executor. The executor would handle all orchestration and execution responsibilities and remove the Docker socket from the functions worker. The executor is an HTTP Server built with Swoole and Utopia using various Appwrite libraries to interact with the database.
-
Using Bref's LambaRuntime to Asynchronously Run Swoole Coroutines as Functions on AWS
Swoole will be shipping something really-really cool that is it's own CLI. You can checkout the development at https://github.com/swoole/swoole-cli and you can start playing with it using the pre-compiled binary distributed under Swoole's releases at https://github.com/swoole/swoole-src/releases/tag/v4.8.7.
- Swoole 4.8.7 has been released
-
How is node compared to other backend tech?
It's been around for more then 8 years. Its a very established project with more the 17k stars https://github.com/swoole/swoole-src
autocannon
-
Optimize Your Node.js API with Clustering, Load Testing, and Advanced Caching
Autocannon GitHub Repository
-
Taming the dragon: using llnode to debug your Node.js application
To make things interesting, let’s send some requests to this server with autocannon:
-
Benchmarking Deno vs Node with GraphQL
Using autocannon, I did the following script to simulate 500 concurrent connections over 30 seconds:
-
A first look at Bun: is it really 3x faster than Node.js and Deno?
We then used autocannon to measure the throughput (requests per second) of each runtime server-rendering our React app.
-
Can we use Pydantic models (Basemodel) directly inside model.predict using FastAPI, if not why?
You could also use tools like autocannon to see how many requests/second you can achieve with various methods. : https://github.com/mcollina/autocannon
-
How to Use Source Maps in TypeScript Lambda Functions (with Benchmarks)
I used autocannon to test the function at 100 concurrent executions for 30 seconds. I also used Lambda Power Tuning to find the ideal memory configuration, which proved to be 512MB. All the results are available.
-
Find bottlenecks in Node.js apps with Clinic Flame
Moreover, if your blocking issue is appearing only on heavy load, you can easily test it using the very nice --autocannon CLI param (see it with clinic flame --help) where you can specificy autocannon options to generate some HTTP load on your web service.
-
Created a URL shortener in Node (Fastify) and in Go (net/http). Why isn't Go faster?
I packaged them both with Docker and deployed them to an EC2 instance, each behind an Nginx reverse proxy I setup in docker-compose. I'm currently testing performance using autocannon from my laptop like this: `autocannon -a 5000 -w 10 URL` (5000 requests with 10 workers), and both apps complete in around 40 seconds. The EC2 instance is in Oregon and I'm testing from Toronto.
-
DB query performance options.
You can test it by yourself using console.time(). You can use autocannon to stress-test your http server to see what is really the best options.
-
Experiments in concurrency 3: Event loops
When I test this with autocannon making three simultaneous requests (autocannon --connections 3 --amount 3 --timeout 10000 --no-progress http://localhost:5678/):
What are some alternatives?
RoadRunner - 🤯 High-performance PHP application server, process manager written in Go and powered with plugins
node-clinic - Clinic.js diagnoses your Node.js performance issues
Phalcon - High performance, full-stack PHP framework delivered as a C extension.
octane - Supercharge your Laravel application's performance.
Symfony - The Symfony PHP framework
serverless-graphql - Serverless GraphQL Examples for AWS AppSync and Apollo
ReactPHP Promises Testing - PHPUnit assertions for testing ReactPHP promises
aws-sam-cli - CLI tool to build, test, debug, and deploy Serverless applications using AWS SAM
Amp - A non-blocking concurrency framework for PHP applications. 🐘
lambda-sourcemaps
React - Event-driven, non-blocking I/O with PHP.