-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-12-25] Benchmark performance bottlenecks when opening chats #50652
Comments
Thanks! 👋 |
Update Who
What
How |
cc @mountiny we'd like to ask you for any feedback about this 1st batch (please invite others!). Is there an area we're missing? I want to make sure we focus on the right parts when profiling this, the exact tools (like e2e suites) will come next once we fully agree on the who&what. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.51-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-10-29. 🎊 For reference, here are some details about the assignees on this issue:
|
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
The extended analytics setup is merged now:
|
also cc @hannojg, do you think these should also be reported to Firebase OR we just focus on being able to profile this behind some flag? |
This comment was marked as off-topic.
This comment was marked as off-topic.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.76-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-25. 🎊 For reference, here are some details about the assignees on this issue:
|
Opened a draft PR and I will proceed with more testing so this can be reviewed from Monday. |
Tested this today, here's an update:
^ is a sample output we get from listing all the local
My one problem I observed today though is that we only collect these behind an environment variable flag of I thought about turning the markers on together with the |
Working on integrating measures into
|
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
Still working on the linked draft PR, reworking the Performance module so it's available during runtime. I'm also adjusting it to fit our style guide. |
Updated the PR, testing this now. |
Job added to Upwork: https://www.upwork.com/jobs/~021873115691475801087 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rayane-djouah ( |
Triggered auto assignment to @laurenreidexpensify ( |
@mountiny the PR got merged but I think we're blocked on evaluating this further given the profiling feature itself is currently broken. Everything is in place though, we're not collecting local metrics to the AppInfo. Should we close this issue? |
Coming from the discussion thread under https://expensify.slack.com/archives/C05LX9D6E07/p1728314452317409
Problem
Lack of solid performance benchmarks across the core app workflows, baselines for proposing performance improvements.
Solution
cc @hannojg
Issue Owner
Current Issue Owner: @rayane-djouahUpwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: