Hey, all.
Uncategorized
3
Posts
2
Posters
1
Views
-
Hey, all. I need to find some examples of small (like, Raspberry-Pi-small) Fediverse instances that shut down because the traffic was too much for them. Do you know of any examples? Blog posts or other URLs with explanations would be helpful.
(Note that this is somewhat different from the thundering herd problem when someone shares a link on the Fediverse to a non-Fediverse site.)
-
Hey, all. I need to find some examples of small (like, Raspberry-Pi-small) Fediverse instances that shut down because the traffic was too much for them. Do you know of any examples? Blog posts or other URLs with explanations would be helpful.
(Note that this is somewhat different from the thundering herd problem when someone shares a link on the Fediverse to a non-Fediverse site.)
@evan that seems unlikely to me. I would imagine most small instances like that would be personal/family instances like mine currently on a Raspberry Pi 4 which handles volume just fine. If they shut down I would assume it would have been for other reasons.
-
@evan that seems unlikely to me. I would imagine most small instances like that would be personal/family instances like mine currently on a Raspberry Pi 4 which handles volume just fine. If they shut down I would assume it would have been for other reasons.
@kaleb thanks Kaleb!
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@brennen I mean, a monocle wouldn't solve your old man glasses, but how cool would it be?
-
@hazelnot now if you're not using vsync what happens? the game still needs to throttle the CPU periodically so the rendering work doesn't get backed up, but generally your options are 1) to ignore vsync entirely and if you get a tear you tear, and 2) wait for the vblanks when you're on time but if you're late just tear anyway. option 1 improves latency when it's early and when it's late, but looks terrible. option 2 only improves latency when the frame is late
-
@Ricciotto @danielcuello this!
secondo me ci sono tre cose distinte: l'autore, l'opera, e quello che succede coi soldi che si danno all'autore
di solito non ho problemi a separare l'autore dall'opera, se l'autore è una persona orrenda su aspetti privati
ma per harry potter faccio un eccezione: a quell'autrice non voglio dare neanche un centesimo, visto come li usa (in compenso continuo a leggere opere ambientate nel mondo di harry potter, ma sono scritte da altri, e non le fanno guadagnare nulla)
(ok, continuo a leggerle anche perché sono mediamente molto migliori dell'originale, ma quella è una questione diversa :D )
-
@morloi Ho appena finito la prima stagione. Delizia.
-
@kenobit lower decks è un piccolo capolavoro. Tutto.
-
@hazelnot since there's some amount of staggering that happens naturally between the CPU and GPU, the end to end latency is usually going to be something in the ballpark of the frame interval * 2. so the CPU submits work within its 16.6 ms, and the gpu completes its work within its own 16.6, and the two will drift within some overlap to a normal total of up to 33.3 milliseconds of total latency when everything is on time
-
@guardaminfaccia mi aspettavo che proseguisse con un 80 enne che riusciva a leggere tranquillamente le scritte sul pacchetto, e poi si alzava e partiva di corsa su un sentiero in montagna
ma forse è perché incontro troppi 80 enni che mi superano sui sentieri di collina :D
-
@hazelnot when vsync is on, and a frame is presented early, the gpu driver blocks the thread that requested a present so that it doesn't run faster than the GPU (this is an oversimplification). when the all of the rendering work is finished on the GPU and it is late, the present stalls until the next vblank before flipping the back buffer. so if you're targeting 60 fps on a 60 fps screen, the normal cadence is 16.6 ms, a hitch is + 16.6 * N where N is how many intervals late you are rounded up
