tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie the concept of web responses as random radiation. Interesting in the age of "AI" popularisation...
-
@sophie shouldn’t it be CPM like a real Geiger counter
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie@catgirl.cloud
this one hosts its website from two floppy drives in raid 1 without cache so it already has a setup where it can hear every access to its site
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie@mastodon.catgirl.cloud
i'm sorry but who ever measures web requests in hertz
-
@sophie and use clicks to indicate each one!
geiger counter here we gooo!!@4censord @sophie I remember talking to someone in the late 90s, early 00s that told me a colleague had tied in a sound generator to their company’s smtp servers, and it would play forest sounds in the background all day in the sysadmin office. I seem to recall that the amount of rain was tied to the load, and different bird calls represented different types and sizes of mail.
It was done in such a way as to be a pleasant background sound, but at the same time, when something went wrong, the sysops would hear it long before monitoring flagged it.
I suspect this system eventually died a death due to moving to a cloud provider, but it does show that monitoring can be something other than visual…
-
@sophie good idea, are they also poisson distributed?
@Quantensalat @sophie Don't open that can of worms. In university I had an entire compulsory 1-semester course on queueing theory.
Rabbit hole exit node: https://en.wikipedia.org/wiki/Erlang_distribution
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
-
@4censord @sophie I remember talking to someone in the late 90s, early 00s that told me a colleague had tied in a sound generator to their company’s smtp servers, and it would play forest sounds in the background all day in the sysadmin office. I seem to recall that the amount of rain was tied to the load, and different bird calls represented different types and sizes of mail.
It was done in such a way as to be a pleasant background sound, but at the same time, when something went wrong, the sysops would hear it long before monitoring flagged it.
I suspect this system eventually died a death due to moving to a cloud provider, but it does show that monitoring can be something other than visual…
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie@mastodon.catgirl.cloud what if the requests are periodic tho?
-
@sophie and use clicks to indicate each one!
geiger counter here we gooo!! -
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie
SI avoids identifying countable entities and events like web requests except in special cases like becquerel (which is specifically for radioactive decay). This is but one example among many where the needs of IT are outside the scope that SI serves.
https://www.researchgate.net/publication/339954122_Quantities_and_Units_for_Software_Product_Measurements -
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie the normal unit for these kinds of things is the Erlang, but you would have to normalize for the number of requests/second per active user.
Perhaps create a new unit? I vot for BernersLee, abbreviation BL.
-
@sophie the normal unit for these kinds of things is the Erlang, but you would have to normalize for the number of requests/second per active user.
Perhaps create a new unit? I vot for BernersLee, abbreviation BL.
@fazalmajid @sophie isn't erlang only applicable to circuit-switched networks like analog telephone, not for packet-switched networks like TCP/IP?
-
@fazalmajid @sophie isn't erlang only applicable to circuit-switched networks like analog telephone, not for packet-switched networks like TCP/IP?
-
@sophie
SI avoids identifying countable entities and events like web requests except in special cases like becquerel (which is specifically for radioactive decay). This is but one example among many where the needs of IT are outside the scope that SI serves.
https://www.researchgate.net/publication/339954122_Quantities_and_Units_for_Software_Product_MeasurementsBq is fine. Network engineers have come to call the unavoidable botnet probing a system will see within minutes after being connected as the background radiation of the Internet.
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
@sophie practically, however, both end up being interpreted as the same
-
tip: web requests should not be measured in Hz [hertz] as that is only used for periodic frequencies, which random events (like requests hitting a web server) are not!
measure them in Bq [becquerel] instead
-
@Quantensalat @sophie Don't open that can of worms. In university I had an entire compulsory 1-semester course on queueing theory.
Rabbit hole exit node: https://en.wikipedia.org/wiki/Erlang_distribution
@hennichodernich @sophie oh wow, but I should have guessed that its a crucial topic
-
@4censord @sophie I remember talking to someone in the late 90s, early 00s that told me a colleague had tied in a sound generator to their company’s smtp servers, and it would play forest sounds in the background all day in the sysadmin office. I seem to recall that the amount of rain was tied to the load, and different bird calls represented different types and sizes of mail.
It was done in such a way as to be a pleasant background sound, but at the same time, when something went wrong, the sysops would hear it long before monitoring flagged it.
I suspect this system eventually died a death due to moving to a cloud provider, but it does show that monitoring can be something other than visual…
@moof But wouldn't it be more prone to just rainy day exploits, upon cloud integration?
-
@4censord @sophie I remember talking to someone in the late 90s, early 00s that told me a colleague had tied in a sound generator to their company’s smtp servers, and it would play forest sounds in the background all day in the sysadmin office. I seem to recall that the amount of rain was tied to the load, and different bird calls represented different types and sizes of mail.
It was done in such a way as to be a pleasant background sound, but at the same time, when something went wrong, the sysops would hear it long before monitoring flagged it.
I suspect this system eventually died a death due to moving to a cloud provider, but it does show that monitoring can be something other than visual…
since it also goes into more detail.
