Open arasHi87 opened 2 years ago
In the past we have used the database to store sessions to achieve the same. I remember talking about making this the default. @ubergeek42 do you remember why we didn’t do this? It would help these kinds of cases (and even help us at the world finals to actually have two active nodes)
In the past we have used the database to store sessions to achieve the same. I remember talking about making this the default. @ubergeek42 do you remember why we didn’t do this? It would help these kinds of cases (and even help us at the world finals to actually have two active nodes)
Is domjudge still support this feature? If so, is there any document? thx
I'm not sure why we didn't do it by default, I guess performance is probably better if you're on a single node and don't need to hit the database for sessions too. But that's probably a tiny impact.
We have a small wiki page which briefly discusses using the session based storage: https://github.com/DOMjudge/domjudge/wiki/Scaling-and-load-testing
But it's basically just follow the symfony docs: https://symfony.com/doc/current/session/database.html
I'm not sure why we didn't do it by default, I guess performance is probably better if you're on a single node and don't need to hit the database for sessions too. But that's probably a tiny impact.
Can we somehow measure this? If the impact is near-zero, I would propose to make it the default.
Cause I deploy domserver in k8s, so I need to let domserver to be scaleable, but I can't find relevant information on the Internet, so I leave my solution here for someone who need this (all we need just to modify the official Dockerfile).
Install dependency
Install php-ext
Set php-ini
Done
And remember to change the redis host to yourself, hope this can helps guy!