Live data from Hacker News

This Blog is now hosted on a GPS/LTE modem

nns.ee

31–40 of 212 posts

Re: This Blog is now hosted on a GPS/LTE modem

#32
post #11

Earlier quoted context omitted.

if it's pure static you can easily server thousands and thousands of request per second no problem.

This website returns 40.5 kB from nns.ee host (with CSS and SVG). 1000 users per second requires 40.5 MB/s or 324 Mb/s connection. Author mentioned that his device provides 10 Mb/s throughput. So realistic number is serving 30 users per second. For some reason his main.css is not compressed, so that would be the first thing to optimize.

Looking at the network requests, the fonts are being served from Google api so not a problem for this.

The CSS on the other hand has TONS of comments which can be gotten rid of and minimized.

Re: This Blog is now hosted on a GPS/LTE modem

#33
post #7
post #6

Earlier quoted context omitted.

It's a static file being served, 32MB RAM nginx instance can handle well past HN traffic for something like that

It uses darkhttpd https://unix4lyfe.org/darkhttpd/

The blog post does state they are using darkhttpd but the network request for the blog post says "Server: nginx". Does darkhttpd use nginx inside or something?

Re: This Blog is now hosted on a GPS/LTE modem

#34

Earlier quoted context omitted.

This website returns 40.5 kB from nns.ee host (with CSS and SVG). 1000 users per second requires 40.5 MB/s or 324 Mb/s connection. Author mentioned that his device provides 10 Mb/s throughput. So realistic number is serving 30 users per second. For some reason his main.css is not compressed, so that would be the first thing to optimize.

Looking at the network requests, the fonts are being served from Google api so not a problem for this. The CSS on the other hand has TONS of comments which can be gotten rid of and minimized.

You're right, removed part about fonts.

Re: This Blog is now hosted on a GPS/LTE modem

#35
This is realy cool!

I wonder if Justine's Redbean[0] webserver, which got recently posted on HN[1], would support ARM in such use case. Its executable size is 460KB, it even allows Lua scripting, and benchmarks 1 million pages per second on desktop PC.

[0] https://justine.lol/redbean/index.html [1] https://news.ycombinator.com/item?id=26271117

Re: This Blog is now hosted on a GPS/LTE modem

#36
post #7

Earlier quoted context omitted.

It uses darkhttpd https://unix4lyfe.org/darkhttpd/

The blog post does state they are using darkhttpd but the network request for the blog post says "Server: nginx". Does darkhttpd use nginx inside or something?

My assumption is reverse proxy via USB localhost

Re: This Blog is now hosted on a GPS/LTE modem

#37
post #16

The Quectel modems are fun parts. We are using one in a project as a kind of theft protection. I couldn't belive at first "this is a whole computer with Linux on it". I really wonder why modem manufacturers feel the need to encapsulate everything so much. Is it for regulatory reasons, to protect their secret sauce, or for our convenience? On the one hand it makes simple things really easy with some AT commands, on th…

> I really wonder why modem manufacturers feel the need to encapsulate everything so much. The alternative would be using an RTOS of some sort, implementing a full network stack (with > 100Mb throughput) and a USB device, as the bare minimum. Then you also have I2S audio, GNSS, etc. It probably makes more sense using an entire OS at some point. BTW, this is typical Qualcomm, that makes the chipsets for these modems.

Why not offload all that to the driver running on the main application processor? The risk of having a second, black-box running Linux is that it’ll get outdated and/or compromised and used as a persistence mechanism for malware.

Re: This Blog is now hosted on a GPS/LTE modem

#38
post #24

Earlier quoted context omitted.

Regulatory reasons. There are a lot of things that FCC regs say that devices that transmit either must or must not do, which made more sense back when everything was analog. Now that the device is a full computer and can be programmed to do whatever you want, the way the industry has decided to best fulfill all those requirements is to make the computer do exactly and only what is required and then lock it down into…

Do those regulations explicitly say that the RF device is not allowed to be programmable by the user? And isn't the user legally forbidden from substantially modifying the RF behaviour in any case?

I can't find it now but there was an article posted a while ago that explained the existence of just such rules back when the very first mobile phones used analogue transmission, which of course was easy to intercept. So the FCC forced radio manufacturers to prevent users being able to tune to those frequencies and additionally specified that manufacturers be responsible for making this limitation very hard to defeat... rather than fix the original problem of course.

Those rules exist to this day but have no relevance. However I suspect there are other similar but slightly more sane rules in play since modems are now just software defined radios that can be made to do nearly anything you want given the right access - i.e you can cause a lot of trouble, even if you don't intend to.

Re: This Blog is now hosted on a GPS/LTE modem

#40
post #35

This is realy cool! I wonder if Justine's Redbean[0] webserver, which got recently posted on HN[1], would support ARM in such use case. Its executable size is 460KB, it even allows Lua scripting, and benchmarks 1 million pages per second on desktop PC. [0] https://justine.lol/redbean/index.html [1] https://news.ycombinator.com/item?id=26271117

gatling [0] is also pretty small and fast, it also can do FTP and SMB if you need that.

[0] https://www.fefe.de/gatling/

Post reply on HN