mholt
High memory usage in l4 matcher
Postgres matcher is taking very high memory even when I am not using it which eventually kills caddy due to OOM. During profiling I have called only imgproxy with 20 concurrent requests .
{
servers {
listener_wrappers {
layer4 {
@postgres postgres
route @postgres {
proxy postgres:5432
}
@redis regexp ^[+\-$:_#,!=\(\*\%\~\|\>]$ 1
route @redis {
proxy redis:6379
}
route
}
tls
}
}
}
:80 {
reverse_proxy /debug/pprof/* localhost:2019 {
header_up Host {upstream_hostport}
}
imgproxy.example.com {
tls internal
reverse_proxy imgproxy:8080
}
}
Actually, a closer look at that profile tree shows that the memory sum is already over 99% -- do you have the rest of the tree? Maybe try svg as well to get the full picture. (Sorry, @metafeather -- might not be a leak in the postgres matcher!)
Hmm, well, maybe not so much a leak as it is just lack of pooled buffers. @metafeather Any interest in using sync.Pool?
@divyam234 How many of your connections are Postgres? What if you reorder the matchers so it's not first?
Reordering results in same result.Its only fixed after removing postgres block.During profiling there were no postgres connection.
Busy server, I'm guessing?
My first thought would be we could try pooling the buffers in that matcher.
If we look closer on the postgres matcher code, we can see here that, for each matching iteration, it reads 4 bytes, then up to 2^32-4 bytes, then processes some of these bytes to decide whether it is postgres or not.
I wonder if we can rewrite this matcher to consume fewer bytes or have fewer loops. There is also a for loop here that doesn't look good to me at first sight, especially given the fact this matcher returns true if at least one "startup parameter" has been found. But I don't have any postgres setup to test it properly.
OH. I didn't realize that at a quick glance. Duh. Yeah, we can probably do better here... (I also don't really use Postgres.) @metafeather Any ideas on how we can improve this?
Noticed the same behavior when using this config that turns Caddy into an exclusive SNI proxy
{
layer4 {
udp/:443 {
route {
proxy {l4.tls.server_name}:443
}
}
tcp/:443 tcp/:80 {
@insecure http
route @insecure {
proxy {l4.http.host}:80
}
@secure tls
route @secure {
proxy {l4.tls.server_name}:443
}
}
}
}
@WGOS, I have the following questions with regards to the config you posted above:
- Why are you trying to proxy incoming UDP packets to a TCP upstream? It seems weird and shouldn't work at all for HTTPS.
- Why are you trying to use
{l4.tls.server_name}when you have no TLS? Note you couldn't have TLS on a UDP port. - Why are you trying to serve HTTPS on port 80 and HTTP on port 443? At least it's not the way it generally works for 99% of users.
In my view, your config should be rewritten to something like that:
{
layer4 {
udp/:443 {
route {
# no TLS placeholders could be used here
# and UDP must be enabled explicitly
proxy udp/upstream.local:443
}
}
tcp/:443 {
@secure tls
route @secure {
proxy {l4.tls.server_name}:443
}
}
tcp/:80 {
@insecure http
route @insecure {
proxy {l4.http.host}:80
}
}
}
}
Finally, the issue we are discussing here is about postgres matcher performance, while you don't seem to be using it at all. In case you keep facing any problems after you make you config valid, please open a separate issue and provide more details.
@vnxme thanks for clarifying. It didn't came to my mind that proxying QUIC wouldn't work with this module.
I did proxy TLS and HTTPS on 80 and 443 ports simultaneously because of me missinterpreting documentation. I will change my config.
As to why I did reply to this particular discussion I felt it might be an issue with tls and http matchers also as I did observe high RAM consumption while using them.