@EmoDuck@sh.itjust.works to Memes@lemmy.ml • 1 year agoTwitter users right nowsh.itjust.worksimagemessage-square322fedilinkarrow-up12.94Karrow-down140cross-posted to: beyondcombustion@lemmy.beyondcombustion.net
arrow-up12.9Karrow-down1imageTwitter users right nowsh.itjust.works@EmoDuck@sh.itjust.works to Memes@lemmy.ml • 1 year agomessage-square322fedilinkcross-posted to: beyondcombustion@lemmy.beyondcombustion.net
minus-squareSquare Singerlinkfedilink6•1 year agoThen the algo recommends the one with the lowest load and hides the others behind a … icon or something.
minus-squareNoodlezlinkfedilink3•1 year agoMm this could be a problem because server load is too unpredictable. I would actually say just randomize the list, so that it kinda does its own “load balancing” by incentivizing to pick whatever random top one it selected?
minus-squareSquare Singerlinkfedilink6•edit-21 year agoYeah, whatever metric. Could also use a mix of number of users, some form of reputation measurement, uptime, etc. I mostly meant that the system should pick a “best server” and recommend that. Smarter people than me can come up with the best metric. But swamping the user with >100 servers to pick from is counterproductive.
Then the algo recommends the one with the lowest load and hides the others behind a … icon or something.
Mm this could be a problem because server load is too unpredictable. I would actually say just randomize the list, so that it kinda does its own “load balancing” by incentivizing to pick whatever random top one it selected?
Yeah, whatever metric. Could also use a mix of number of users, some form of reputation measurement, uptime, etc.
I mostly meant that the system should pick a “best server” and recommend that. Smarter people than me can come up with the best metric.
But swamping the user with >100 servers to pick from is counterproductive.