-
Notifications
You must be signed in to change notification settings - Fork 6
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
Large volume of transactions causes memory depletion #54
Comments
It doesn't create a large number of connections. It just queues a huge backlog of queries to execute. This is not exactly a bug, because each This is comparable to the real-life scenario where you wouldn't pay an employee their salary every hour even though their wage is measured hourly. I consider this issue as a wontfix for now, but any suggestions to improve this would be welcome. |
I don't think there are actually many situations to add money per tick, but the more currency and number of players, the more likely this is to occur. |
In that case you should increase the number of workers in the libasynql settings. |
If the database server is slow and takes a long time to process transactions, attempting to process a large number of transactions will
create a large number of connections andcause the server to crash due to lack of memory.Using slow database, you can reproduce it with code like this
The text was updated successfully, but these errors were encountered: