-
Notifications
You must be signed in to change notification settings - Fork 72
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
Enabling WF generate too much logs #461
Comments
The branch reduced the logs back to normal, but also improved performance significantly ?? Fillrandom X2 vs the WF before and overwrite is 50% better, makes it almost X3 more than without WF. Large obj test is running |
It does makes sense … write to log with the freq it was delayed things .. אז פצצות לגבות Sent from my iPhoneOn 14 Apr 2023, at 12:57, erez-speedb ***@***.***> wrote:
The branch reduced the logs back to normal, but also improved performance significantly ??
Small Obj
https://admin.speedb.io/performance?
items=1qSNtYwD7s1rFU6mOjiA&items=bbnH4HiAhbm13TMK0a36&items=KGP7PbR6tEVMduQAmWqW&items=eFKIsbYQ8H7XSkYOLJaM&colors=%23F06292&colors=%23BA68C8&colors=%2300796b&colors=%2300acc1&colors=%23BA68C8
Fillrandom X2 vs the WF before and overwrite is 50% better, makes it almost X3 more than without WF.
Large obj test is running
@Guyme @ayulas @hilikspdb FYI
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The large obj shows improved performance as well However, the problems also become distinguish, the memory consumption is higher than before and the disk usage is also a scale more than without WF. |
Under the restriction, passed performance tests |
The logs for "normal" large obj test is about 30 MB,
The WF test was over 6 GB.
In the huge 2.5 TB DB test, the logs were so big that the test failed with no space left on the device, meaning ~1 TB of logs.
The text was updated successfully, but these errors were encountered: