Phabricator VS locust

My company has used Phabricator, which is an alternative to Azure Devops, for about 5 years. A few days ago they announced that the project won't be maintained anymore, so we are looking into alternatives. We have around 50 devs+product folks that use Phabricator at the moment. Source: almost 3 years ago

You also mention Gitlab is close to what you would like - maybe Phabricator is even closer: https://phacility.com/phabricator/. Source: about 3 years ago

Https://phacility.com/phabricator/ I think checks most of those boxes, maybe all. Source: about 3 years ago

Finally, let's compare the response time of the requests. For that, we will use Locust , an open source load testing tool. The tests will run for 5 minutes, and will increase 4 requests per second every second until they reach 1000 requests per second. - Source: dev.to / about 2 months ago

Locust: Another open-source tool, Locust is particularly flexible due to its support for Python scripts. It can conduct load tests across multiple machines, making it possible to simulate millions of users simultaneously. An exceptional feature of Locust is its web-based UI, which allows real-time tracking of performance metrics during test execution. - Source: dev.to / about 2 months ago

Locust is a perfect tool to use on such occasion:. - Source: dev.to / 2 months ago

So, in theory, we can handle 300 requests per minute on a single server which was the assumption we started with. After this, I decided to play with this configuration and see what we could achieve. But, to go ahead I need a system to measure the metrics of our load testing. So I quickly set up Locust on my system. Locust is an open-source easy to setup load-testing framework. - Source: dev.to / 2 months ago

The OpenTelemetry Demo is composed of microservices written in different programming languages that talk to each other over gRPC and HTTP; and a load generator which uses Locust to fake user traffic. - Source: dev.to / 6 months ago