Open ericboucher opened 5 months ago
/bounty 50
/attempt #1111
with your implementation plan/claim #1111
in the PR body to claim the bountyThank you for contributing to WFP-VAM/prism-app!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🔴 @tobihans | Feb 26, 2024, 4:22:57 PM | WIP |
🔴 @feliciien | Feb 29, 2024, 7:04:41 PM | WIP |
🔴 @Bhavyajain21 | Mar 20, 2024, 7:08:41 PM | #1169 |
@ericboucher can I be assigned?
@mehulmathur16 any luck?
Hi @ericboucher, I got caught up in some other works. I'll setup the codebase and check this out today. Will update you regarding this.
@ericboucher I wasn't able to find anything specific for load time differences. Also on my machine, the performance was near about same on both the browsers. Hence, unassigning myself from the issue.
/attempt #1111
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@feliciien | 5 bounties from 1 project | MDX, Rust, JavaScript & more |
Cancel attempt |
@feliciien any luck? I might close this issue otherwise since we don't seem to be able to replicate well.
@ericboucher I'd like to give it a try. Please assign
/attempt #1111
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@Bhavyajain21 | 6 bounties from 2 projects | JavaScript |
Cancel attempt |
It seems that charts are loading much faster on Firefox than Chrome, even when working with new requests.
Let's investigate where the difference could stem from between the two and improve performance on Chrome if possible.