upvote
> Nginx’s real strength was being able to proxy and cache HTTP using that same mechanism

Fun fact: Igor Sysoev originally wrote mod_accel [1], an acceleration and reverse-proxy caching module for Apache before he made nginx.

I remember using that module in the mid-2000s as a load balancer (and to offload SSL encryption/decryption as it was a CPU-expensive operation).

[1] http://sysoev.ru/en/apache_modules.html

reply
We've barely even started on optimizations like advanced language aware grammars, and specialization routing (dynamically loading fine tunes or seperate weights for specific tasks or languages).
reply
Right. But those still sound like modest gain territory, or qualitative gains within the same rough performance, rather than the "breakthrough" improvement notion I was responding to.

My naïve impression is that the LLM world will keep delivering these fractional improvements for some years at the cost of simplicity. And sure, ontological support seems quite promising.

But making things radically better or faster for small models in the way that is hypothesised, that feels like it can only come as a result of hardware performance improvements and likely architecture changes.

Because there's no free lunch, right? Speculative drafting for example, noticeably improves performance until acceptance rates drop for reasons that have to do with the particular application, and then it starts hurting you, especially near the limits of the memory bandwidth. Because once it is wasteful it is an extra overhead.

I gather Gemma 4 supports, in principle, dynamic speculative draft lengths, to help with this — where it will stop making bold predictions when the success rate falls. But I'm not sure if any of the inference engines I've tested with support that.

I think small models are miraculous — I still think Gemma 4 12B is astonishing — but I guess what I am saying is that I think maybe technology is moving quickly enough that the developers are done with the low-hanging fruit.

reply
The gains wouldn't be "free lunch", it's the result of time and effort researching optimal design and architecture.

Even if the idea of "no free lunch" was taken liberally discounting the cost of research, it would only be limiting to systems built from a foundation of optimization, but that's not the case. The foundation so far has been one of brute force scaling. Usually meaning there is lots of room for optimization.

reply
> The foundation so far has been one of brute force scaling.

In cloud AI, sure. But in the smaller open weights model territory it feels like we're well into optimisation?

reply
[dead]
reply
Also lighttpd! Released in 2003, one year before nginx (2004)
reply