-
Notifications
You must be signed in to change notification settings - Fork 264
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
Optimising the DB Search #4388
Optimising the DB Search #4388
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4388 +/- ##
=======================================
Coverage 85.27% 85.28%
=======================================
Files 282 282
Lines 31209 31209
=======================================
+ Hits 26615 26618 +3
+ Misses 4594 4591 -3 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Anirban Biswas <[email protected]>
Signed-off-by: Anirban Biswas <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the patch, but I don't see how it changes anything to the actual code.
Actually this PR is improving the readability and the error handling of the process which somewhat improving its optimization. We can use Cache Memory by Hashmaps to improve the DB calls should I go with that method ? |
I need proof of that. Readibility, yes, a bit, but I'm not sure it improves optimization from the compiler. From the compiler point of view, once reduced to a simple form, there is no difference between the two versions. |
Sir Can I use Cache Hashmaps to improve optimization ? |
You can try for sure. I cannot merge this PR since it doesn't do anything useful and clearly not what the description claims. |
Signed-off-by: Anirban Biswas <[email protected]>
Advantages :
olmMachine.getRoomSettings()
#4337