Potential memory leak

[oxyno-zeta]

Potential memory leak

[armin-malek]

thanks, it has solved the problem!

PS: Out of this, do you use s3-proxy to make a tile map server ?
no it is just serving images from a private bucket for a machine learning project

[oxyno-zeta]

Hello @armin-malek ,

Thanks for your issue.

I never used this provider so I can't say if it is coming from this or not.
But I have other ideas in mind. Can you answer those questions please ?:

• Do you have a lot of requests on your server ?
• Do you have a lot of different path on your requests ? (/mybucket/file1, file2, file3, ...)

Regards,

[armin-malek]

we have close to 8 million files in the bucket
and we serve around 7 objects per second (in reality it's a burst of 30 to 40 objects every few seconds),
the average object size is around 70KB

[oxyno-zeta]

I think I have an idea of why.

People requesting different files all the time ? Or are they the same for multiple minutes ?

[armin-malek]

it's like an image hosting platform so yeah it should be mostly random objects

[oxyno-zeta]

Ok so I think I know why. This must come from prometheus metrics which are saving metrics per "request path". This can be patched for sure.

[armin-malek]

Ok so I think I know why. This must come from prometheus metrics which are saving metrics per "request path". This can be patched for sure.

I'm not familiar with the code base but maybe an option to disable the metrics in the config file should do the trick
for now, i'll keep restarting the container every once in a while :)

[oxyno-zeta]

I've just released a new version. The 4.13.0 release have a configuration dedicated for this.

Here is an example:

# Metrics configuration
metrics:
  # Disable router path save in HTTP metrics
  disableRouterPath: true

That should fix your problem.

PS: Out of this, do you use s3-proxy to make a tile map server ?

[armin-malek]

out of this too
currently it's logging every request to stdout, is there way to disable that too? i couldn't find it in the docs
if i'm not mistaken writing to stdout is not exactly cheap
what other log levels we have in the config file?

[oxyno-zeta]

Cool to hear this ! That's great!

Yes that's a feature to log everything. You can change the log level to error if you want only errors. All log levels from uber/zap logger are supported.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days