Technology
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
I totally be interested in this sort of testing methodology being published. Maybe in a wiki?
Getting comparable numbers for buffer bloat and queuing would be great for commercial routers. Of course you would want to compare against Enterprise solution so that people know where on the spectrum they're landing.
Full disclosure I roll my own GLI net open WRT router and I enforce different queues for qos seperation.. i.e. downloading and streaming shouldn't interfere with VoIP calls and gaming
Multi client test seems better honestly. I end up running 3-4 iperfs from different clients to a wired server to see how the bandwidth chokes. I wonder how it will be if one of the clients are running the iperf server as well.
Real life workloads like 4k and VoIP with multiple clients seem much more realistic and representative.
Seriously Lemmy is the best. Few minutes in and people are already answering questions. The concept behind the multi-client tests are to SSH into the server and then simulate whatever type of traffic one wants. I have already done it on a couple of wireless routers and it worked great. I hope at least. Iperf can't really accomplish this, as far as I know, it's only one instance on a single client at a time. Netburn seems to be the best tool so far, while keeping things free and open-source.
Seconding your opinion about lemmy :) Do you think you could write up that you did? I would be interested in reading. Found this article on ars as well:
https://arstechnica.com/gadgets/2020/01/how-ars-tests-wi-fi-gear-and-you-can-too/
I'll be checking out netburn.
I am not really a fan of self promotion and I would really like Lemmy to be free of it, as much as possible. If you want to check what I did so far, just write "router review multi-client stress test" in any browser. You really won't find anybody else trying out these tools at the moment, even Arstechnica seems to have moved away from wireless router reviews.
Sure :)
I recently ran into an issue with my home network where I suspected that the current wifi router (3-point mesh) couldn't handle all the clients simultaneously. Not in a manner of throughput, but just with keeping all the devices online in the first place.
I have at minimum 30 clients online all the time, up to a max of 40 or something, depending on who's home or what is active. (Went a bit overboard with home automation and stuff.)
I was getting random disconnects or stalling wifi on some of the devices. The coverage was fine, so I figured it was just the number of wifi signals that was overwhelming the AP.
Point of the story: I was disappointed that absolutely no review/benchmark ever pays attention to this kind of upper limit that seems to exist in practice. It's all range and speed, but never about the maximum number of active clients.
I've replaced the mesh network and everything is fine now. But I had to trial and error that shit...
It isn't really about the maximum number of client devices, it's what they do, what type of standard are they a part of, how far away, the interference (!). This is why it's pretty much impossible to put a number and say: hey, this TP-Link router will handle 30 client devices, while this Asus router goes up to 100.. In a sense, a multi-client stress test kind of addresses this issue, but it kind of doesn't. It's because it's extremely dependent on the conditions that the tester has in their lab/office/home.
One thing to check on a review could be the attenuation as a better factor than the distance (this way, you can reproduce the result in your house even if just with a single-client test).
Not really, to be honest. I'd rather see how compatible a particular router is against popular open-source firmware, how frequently the updates are delivered, etc.
For instance, the Asuswrt Merlin is a pretty good firmware for ASUS routers, but the updates (stable) are irregular - the last stable update currently was two months ago, which to me is unacceptable considering there have been critical vulnerabilities in ASUS routers. Given how malware and botnets are increasingly targeting routers these days, it's imperative that updates get delivered at least once a month - with an out-of-band policy for critical vulnerabilities.
When I run iPerf tests I almost always use multiple clients because of exactly what another comment said, it's more realistic and a better representation.
So you basically spawn multiple instances of iperf3 and then connect all clients to a single server (using the same port?) What do you think about checking the latency experienced at the client level when various tests are running at the same time?
Yeah, I spawn multiple instance of iperf3. Checking the latency would be a very useful metric, it should give a good result of what the connection will be like under load.
One client downloading a torrent, second client viewing 1080p60 video from YT and clients 3&4 transferring a few TB of data through lan.
I would love to see this via WiFi.
Sounds good to me