We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Every day I have to execute set send_logs_level='debug'; to see Peak memory usage
set send_logs_level='debug';
Peak memory usage
Can it be exposed like this
4 rows in set. Elapsed: 11.327 sec. Processed 200.02 million rows, 1.60 GB (17.66 million rows/s., 141.27 MB/s.) Peak memory usage (for query): 1.25 GiB. 3 rows in set. Elapsed: 7.776 sec. Processed 100.01 million rows, 800.08 MB (12.86 million rows/s., 102.89 MB/s.) Peak memory usage (for query): 9.75 GiB.
OR
4 rows in set. Elapsed: 11.327 sec. Processed 200.02 million rows, 1.60 GB (17.66 million rows/s., 141.27 MB/s.). Mem: 1.25 GiB. 3 rows in set. Elapsed: 7.776 sec. Processed 100.01 million rows, 800.08 MB (12.86 million rows/s., 102.89 MB/s.). Mem: 9.75 GiB.
+The same for HTTP headers.
The text was updated successfully, but these errors were encountered:
Nice one!
Sorry, something went wrong.
reverted #52598
Successfully merging a pull request may close this issue.
Every day I have to execute
set send_logs_level='debug';
to seePeak memory usage
Can it be exposed like this
OR
+The same for HTTP headers.
The text was updated successfully, but these errors were encountered: