Mima-samaYou know what I'm gonna blame both #Squid and the #browser for this.
Even though #Polipo is no longer being developed or maintained, Squid's performance still doesn't seem more advanced than it (Polipo for example can fully pipeline requests and responses, and even had multiplexing before #HTTP2, while Squid can only pipeline up to 2 requests). So I suspect Squid itself may be hampering my UX. The only reason I'm even using it is because of the ssl bumping.
I also blame the #browsers because it uses the
I'm never going to get the same latency savings and performance gain with forward #proxy as webmasters do with CDN as gateways, no matter how hard I try 
RE: https://makai.chaotic.ninja/notes/9ymyzzdkug
Even though #Polipo is no longer being developed or maintained, Squid's performance still doesn't seem more advanced than it (Polipo for example can fully pipeline requests and responses, and even had multiplexing before #HTTP2, while Squid can only pipeline up to 2 requests). So I suspect Squid itself may be hampering my UX. The only reason I'm even using it is because of the ssl bumping.
I also blame the #browsers because it uses the
CONNECT #HTTP method for proxying HTTPS. That tunneling already adds RTT compared to just using regular methods like GET (which does support proxying both HTTP and HTTPS and is used by the browser for proxying plain HTTP) and it adds up real quick when you have to deal with a lot of domains being loaded.I'm never going to get the same latency savings and performance gain with forward #proxy as webmasters do with CDN as gateways, no matter how hard I try
RE: https://makai.chaotic.ninja/notes/9ymyzzdkug
:mima_rule: Mima-sama (@mima)
Idk what I expected but wow my #Squid with ssl bumping couldn't just keep up with all the requests I do while normally browsing, and I'm the only user lol. I'm not sure what is the biggest bottleneck, it could be the Yggdrasil (it adds a tiny bit latency but I'm connected directly as a peer), the ssl bumping (even though I've switched from 4096-bit RSA to 256-bit ECC, though I suppose dynamically generating all those certs for each domain is still not trivial), or the VPS itself (it only has a single vCPU and 2GB ram, but the latency should be negligible at around 5-7ms)... It seems the forward #proxy as a concept didn't get much optimizing love in contrast to gateways/reverse proxies like nginx :satsuki_sadge:
Job Bautista
Gioyosemite 
