-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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-08-14] [$250] MEDIUM: [Debugability] Add profile trace download option to Desktop and Web #43363
Comments
Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext. |
Job added to Upwork: https://www.upwork.com/jobs/~018b1cc2a053306cc3 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani ( |
@jayeshmangwani Huh... This is 4 days overdue. Who can take care of this? |
Waiting on proposal, bumped on #expensify-open-source |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Hey, Hanno from Margelo here 👋 we built react-native-release-profiler the library we use on mobile for recording performance profiles. We can enable recording profiles for desktop (and web), by adding web support to the library. |
Hey, Kiryl from Margelo here 👋 @hannojg asked me to work on this task. Can you please assign me on this task? 👀 |
@hannojg, @kirillzyusko, @jayeshmangwani Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I'm working on this task. At the moment I can capture profile traces and I'm discovering the best option for representing this data (obviously it has to match Google Chrome parser standards). Right now I have two options:
I think tomorrow or the day after tomorrow the PR will be ready for review 👀 |
Not Overdue! Kirill is working on this issue. The last update is here, and the PR will be ready for review in a day or two. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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-08-02. 🎊 For reference, here are some details about the assignees on this issue:
|
Issue is ready for payment but no BZ is assigned. @lschurr you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@lschurr)
|
@lschurr Issue is not ready to be paid out yet. The original PR was reverted due to a regression, and a new PR was just merged 3 days ago. Please keep this issue open until the new PR has been in production for 7 days. |
Can you link the new PR here @jayeshmangwani? |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.17-2 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-08-14. 🎊 For reference, here are some details about the assignees on this issue:
|
Payment summary: Due to the regression, payments are half.
|
Requested on ND as per #43363 (comment) |
$125 approved for @jayeshmangwani |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
What performance issue do we need to solve?
e.g. memory consumption, storage read/write times, React native bridge concerns, inefficient React component rendering, etc.
Desktop and web performance is currently difficult to evaluate compared with mobile because we don't support profile tracing
What is the impact of this on end-users?
List specific user experiences that will be improved by solving this problem e.g. app boot time, time to for some interaction to complete, etc.
Desktop and web users are unable to have their performance issues fully triaged.
List any benchmarks that show the severity of the issue
Please also provide exact steps taken to collect metrics above if any so we can independently verify the results.
Triaging this issue would benefit from having a profile trace
Proposed solution (if any)
Please list out the steps you think we should take to solve this issue.
Add web support to react-native-release-profiler
Make the "share profile" flow work on web as well
Add profile trace functionality to the desktop and web apps, in the Troubleshoot menu and four-finger-tap menu
List any benchmarks after implementing the changes to show impacts of the proposed solution (if any)
Note: These should be the same as the benchmarks collected before any changes.
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @muttmuure
Slack conversation:
View all open jobs on Upwork
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jayeshmangwaniThe text was updated successfully, but these errors were encountered: