Posted by andros 1 day ago
Not right. As soon as I saw the box (when the other article was posted), my immediate thought was that it was distracting, frankly a bit creepy (even just the counter is so), and obviously ripe for abuse. About one second after I had the thought, I saw it happen in real time.
> The goal, I suppose, was twofold: (…) and to make the article look bad in front of the aggregators and networks where it was being shared.
I think you’re reading too much into it. I bet all (or essentially all) the people doing that don’t care one iota about you or how you look to whatever aggregator and network. They’d write those same things on an empty wall if you gave them a can of paint. You gave them an avenue and they used it, simple as that.
Hard to take this seriously without the loadtest with the the large number of concurrent users.
For a number of users concurrently reading a long-tail blog post - you will get good results even using DotCom era HTTP polling.
---
See:
Django LiveView vs Phoenix LiveView: a real benchmark
https://en.andros.dev/blog/80134668/django-liveview-vs-phoen...
Django LiveView vs Phoenix LiveView: a real benchmark
https://en.andros.dev/blog/80134668/django-liveview-vs-phoen...
this can't be true, If that hardware can run Django and Phoenix, it for sure can handle orders of magnitudes more concurrent clients than 50 even before you start tuning the OS and the runtime.
> Playwright headless Chromium
maybe you mean you're unable to generate more than 50 concurrent clients using Playwright+Chromium - but that's the wrong tool for loadtesting.
Loadtest should run from a different machine or cluster of machines/VMs. You can generate up to ~ 64K outgoing connections per IP address / alias. With 17 IP addresses/aliases you can generate up to C1M.
That's for a single node.
Then try multiple nodes / cluster - C1M, C2M, C10M, etc.
Also, all concurrent clients should send periodic pings / keepalives and do something useful (e.g. some CPU work, not just being idle).
Then you'll have to change your conclusion from:
> The data answers my original question: yes, Django LiveView holds up against Phoenix LiveView. In day-to-day operations they are practically equal.
to
> The data answers my original question: yes, under *toy* load Django LiveView holds up against Phoenix LiveView. For *toy* operations they are practically equal.
Oh my bad are yall under the impression that HN is not the majority of the traffic right now lmao