-
Notifications
You must be signed in to change notification settings - Fork 0
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
log matches #3
Comments
Understood. |
I wonder if writing to a text file is not faster. csv format for eg? |
from what I know, writing to a text file (the hard drive) takes more ressources |
After a few searches on google, it seems that the performance of this two methods depends mainly on the server's general performance and the size of the data to be stored/read. But in summary, the profitability of the use of a DB increases with the amount of data. And, as the plugin will edit the log data for each query, it is more than probable that two or more requests happen at approximately the same time. If we use a text/raw file, we will have to handle this specific case (and may be some others). |
since there will be a lot of data when log is enabled, please use a database |
log queries, patterns and variables in its own table so admins can review it to optimized the results
make it optional to log the results, so for performance reasons or if everything is right, logging is disabled
The text was updated successfully, but these errors were encountered: