this post was submitted on 12 Aug 2024
89 points (95.9% liked)

Opensource

1120 readers
34 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient

⠀

founded 11 months ago
MODERATORS
Vacant@programming.dev
89
LibreSpeed: Speedtest No Flash, No Java, No Websocket, No Bullshit. (github.com)
submitted 1 month ago by sag@lemm.ee to c/opensource@programming.dev
11 comments fedilink hide all child comments
 

cross-posted from: https://lemm.ee/post/39429103

you are viewing a single comment's thread
view the rest of the comments
[–] kolorafa@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

On the server side to send you data, using any web server with mmap support will probably be less CPU intensive than app that handles websocket, but yes, the details matter as when reading a lot of small files vs websocket, then websocket could be better for CPU usage especially when you could generate data.

But once again using plain old http allow you to use the speestest software against any CDN very easy IMO.

[–] Boomkop3@reddthat.com 1 points 3 weeks ago

Adding headers and some other minor requirements is slower than not. That's really the difference, it's not complicated.