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
LPD-25578 Avoid the cacheless DynamicQuery #150240
Conversation
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
For tests, you can follow the steps in #150234 (comment) For SQL log, you can follow these: Steps to do sql log profile with benchmark tools on specific portal version
Please do SQL logs for Login on the baseline and this pull request. By the way, the portal version for the test and sql log should be the same one, for example, if you pick version A as baseline to run test, also use it to do the sql log. Lily |
Merged. Thank you. |
Update from @victorhcunha: |
Hi @shuyangzhou ! Please let me know if any other adjustments are needed. |
@victorhcunha @slnn why the tests are still using the old benchmark settings? check your portal-ext.properties, it still disables tons of stuff. We must test with out of box settings. |
Hi @shuyangzhou! Here are the new results: Login Testcase
DocumentLibrary Testcase
WebContent Testcase
AssertPublisher Testcase
More details you can check in this google doc (with the files from Login Testcase SQL log) cc @slnn |
The sql log can confirm: But the profile snapshot is broken, both before/after is showing "CPU was not profiled" and nothing was recorded. Please check and fix it. @victorhcunha @slnn |
OK, got it |
Hi @shuyangzhou The cpu sampling issue has been fixed in https://github.com/dantewang/liferay-benchmark-ee/pull/719 By the way, I also checked for cpu tracing, memory profile, all of them work well. Lily |
@victorhcunha please rerun the sql log profile for login test case, for now, keep this as a routine for daily monitor. And link the archive in the daily monitoring spread sheet. |
Hi @shuyangzhou ! When the https://github.com/dantewang/liferay-benchmark-ee/pull/719 is merged, I will add the SQL log record to the daily Login monitoring in our spreadsheet. |
@tinatian @vicnate5 please backport for LXC, thanks!
@victorhcunha This is supposed to drop DB usages on all test cases too, please check.
Also I need the sql log profile for login test case with this fix, @slnn please guide @victorhcunha to do this, thanks!