ddosify VS barrier

DDosify: https://github.com/ddosify/ddosify

We are thrilled to announce the release of Ddosify Self-Hosted on GitHub today. Unlike the Ddosify Engine, this version features a No-code UI and supports distributed traffic generation.

Ddosify is built with ease of use and flexibility in mind, and it supports popular web protocols. It allows you to define and customize test scenarios, generate realistic loads, and monitor performance metrics in real time.

We have organized this write-up into two parts to demonstrate two different features of Ddosify. In the first part, we will perform a load test on a GET endpoint that accepts base and target currency and returns their exchange rate of them. The rand() utility method is used to send different currencies on each request. In the second part, we will test a POST endpoint that performs exchange operations. We will use a CSV file that contains test data stored on our Test App's Database. Then we import this CSV file into Ddosify to replay the same transactions stored on DB, but in high concurrency. In both parts, we will gain insights into the reliability of our exchange API across high traffic.

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.