Are the speeds recorded in Cloudron really MBps or is it Mbps?
d19dotca last edited by d19dotca
Really minor issue (if even an issue at all), but I just noticed yesterday that the transfer speeds recorded in Cloudron (when restoring from backups or backing up for example), it says something like
@10MBps. Note the capital M and B which signifies Megabytes. Full example:
Uploading backup 6962M@10MBps (mail)
Normally however, bandwidth/transfer speeds are recorded in Megabits per second rather than Megabytes per second, which means it should be represented as
@10Mbpsinstead (note the lowercase B).
So I guess my question is... is the way it's recorded in Cloudron as
MBpsactually correct here? If it's Megabits per second then it should all be signified with a lower-case M instead of capital (i.e.
Again, incredibly minor, but figured it is best to always be as accurate as possible and should be a very easy change if it's in fact inaccurately represented as-is currently. Also if it is actually MBps, can we maybe look at representing it down the road as Mbps to match the industry standard measurement?
This is as of version 7.0.4 by the way.
FYI (for anyone reading who may not know the difference), 10 Megabytes per second translates to 80 Megabits per second. Basically 8 Megabits per 1 Megabyte. Your internet speeds at home (when running something like speedtest.net) are represented with Mbps (Megabits per second) rather than MBps (Megabytes per second).
Actually, it is often the case that link speeds are recorded in Mbps (such as your internet connexion bandwith), but transfer speeds are recorded in MBps (such as the download speed of a file in a web browser).
Yes, it is very confusing, even for people who know these things...
Also if it is actually MBps, can we maybe look at representing it down the road as Mbps to match the industry standard measurement?
As such, I do not agree with this part. It would be better IMO to keep MBps in this spot, as it represents a transfer speed, and it is easier to reason about (if you know your backup is roughly 1GB, and the transfer speed is 2MBps, you can easily calculate that it's gonna take ~500s).
The value is calculated in the end from nodejs' stream chunk length. Which as far as I understand is bytes not bits. So I think the UI is correct there then?
d19dotca last edited by
Ah okay, totally fair then. I’ve not personally noticed things represented in MBps but if my experience doesn’t match the usual that others see then I can appreciate that view. thanks guys.