-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Image][Performance] Better caching for iOS images #10792
Comments
📣 @Szymon20000! 📣 |
Triggered auto assignment to @stitesExpensify ( |
Switching this to weekly |
@Szymon20000 I saw you put up a draft PR but you weren't sure about the change because right now FastImage isn't compatible with Fabric. Overall I think we should prioritize Fabric compatibility over using FastImage. Looking into FastImage some more, it seems like one of the main things it handles is persistent image caching. However, that functionality feels potentially in-scope for our persistent storage library Onyx. Going to add this issue to the image tracking issue here |
Any new thoughts here @Szymon20000? |
Been a minute.... let's see... If so, I reckon I should be too since I'm the the BugZero (BZ) team person for that tracking issue. Also... @roryabraham and/or @Szymon20000 , is this actively being worked on? If so, any update? |
Yes, I think so.
Definitely not by me – I don't think there's been any active development on this. |
Bumped to weekly cuz on hold |
Hmm ok well I've been OOO for the week 1 & 2 updates so haven't reached out yet. It looks like there still hasn't been movement on the upstream PR (DylanVann/react-native-fast-image#953) so I say we can try to reach out to see if the maintainer has time to look at the PR this week - and then if there's still no movement by EOW we fork & work on our own version |
Ok reached out, I'll post back here if I get a response |
@Beamanator @mallenexpensify This might be ready for payout by tomorrow, so before we do that I want to clarify how do we handle the payment for this one. I reviewed two PRs for this issue:
Both the PRs were extremely complex and tedious to review. @Beamanator had also mentioned about the pay bump for the first PR review here and overall both the PR codes are a lot different. Can we please increase payout for this one to accommodate the complexity and number of PRs. |
Thanks @mananjadhav, this is definitely a tricky one. I'm going to start an internal discussion, hang tight plz... |
@mananjadhav after internal discussion we believe that $4k, in total, is a fair amount, based on the complexity and also because of the regression. Do you agree @mananjadhav ? |
Thanks @mallenexpensify. Agreed it is fair :) |
@mallenexpensify Quick bump on this one. |
Job added to Upwork: https://www.upwork.com/jobs/~019ac837ee43fe141c |
Current assignee @mananjadhav is eligible for the Internal assigner, not assigning anyone new. |
@mananjadhav can you please accept the job and reply here once you have? |
Accepted @mallenexpensify |
@mananjadhav paid $4000. I'm guessing this doesn't need regression test steps added. @Beamanator can you confirm? And close if so? Thx |
@mallenexpensify the reporting bonus contract is still unpaid for me. |
Thanks @parasharrajat , I missed it as I paid Manan on a different Upwork job. |
@mallenexpensify good question, I believe you're right, I think we can close this out - also @trjExpensify it looks like you added the upstream PR link to the issue title, but I made this issue to track that PR here: #14382 I think this is better so we can close out this very large issue, thoughts? |
Ah yeah, totally. That was before we went the fork route. Make sense. We good to close this out then? |
Aah that makes sense. Ya I'm happy to let @mallenexpensify close it, not sure if all the payments are done |
All paid! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
What performance issue do we need to solve?
Better caching for iOS images
What is the impact of this on end-users?
Previously seen avatars/assets will show up faster with suggested change.
List any benchmarks that show the severity of the issue
Proposed solution (if any)
Use FastImage for Avatars and images that are par of the messages.
Avatar.js
uses Image from react-nativereact-native-render-html - that as far as I know is used for rendering attachment (among the other things) uses Image from 'react-native' if the change with avatars will give us good results it's worth to test patching that library as well. So that it uses fast-image.
List any benchmarks after implementing the changes to show impacts of the proposed solution (if any)
Platform:
Where is this issue occurring?
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Upwork URL: https://www.upwork.com/jobs/~013a8690a2c460efd2
View all open jobs on Upwork
Reported by: @parasharrajat originally on this issue.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: