Skip to content

test: JWT Cache Memory usage grows quickly #4107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
steve-chavez opened this issue May 28, 2025 · 0 comments
Open

test: JWT Cache Memory usage grows quickly #4107

steve-chavez opened this issue May 28, 2025 · 0 comments
Labels

Comments

@steve-chavez
Copy link
Member

steve-chavez commented May 28, 2025

Problem

Doing:

$ postgrest-bench-k6 10 k6/GETSingleUniqueJWT.js 

And monitoring with:

watch -n 1 'ps -p $(pgrep postgrest) -o %mem,rss,vsz'

Makes the memory usage increase fast:

%MEM   RSS    VSZ
54.9 250496 1073793376

As seen on:

Screencast.from.05-28-2025.02.59.28.PM.webm

Solution

#4084 would be a solution, I've manually tested there and memory usage only reaches 12% and is maintained there.

But we really need a way to test this. Try using psrecord to do it.

Notes

  • For some reason, using OPTIONS requests k6/OPTIONSUniqueJWT.js doesn't have the same memory effect as doing GET k6/GETSingleUniqueJWT.js. With OPTIONS the memory increases but quickly goes down and is maintained at ~8%.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants