Skip to content
This repository has been archived by the owner on Nov 13, 2022. It is now read-only.

[BUG?] Look Into Optimizing Loading Speed for Web3 #65

Open
AlphaSerpentis opened this issue Jul 31, 2021 · 4 comments
Open

[BUG?] Look Into Optimizing Loading Speed for Web3 #65

AlphaSerpentis opened this issue Jul 31, 2021 · 4 comments

Comments

@AlphaSerpentis
Copy link
Member

File(s): frontend/???
Test Files Required?: No
What Testing Should Include:

  • N/A

Currently, it may take between 10 - 15 seconds to load the vaults completely (with 400 Mbps down). This delay is somewhat a nuisance and not ideal. Look into figuring out ways to optimize loading speeds.

@tylerferrara
Copy link

tylerferrara commented Nov 23, 2021

@AlphaSerpentis I saw your gitcoin posts on the various page re-designs.
Spinning up the local web server, I noticed there was a noticeable bottleneck in performance from various dependencies. I'd love to take the time to profile your web pages to identify exactly where this bottleneck is coming from. Here's the steps I would take:

Improving Performance

  • Profile render times (Google Lighthouse tool)
  • Identify which components or dependencies are causing bloat
  • Propose component changes & server side rendering to improve "TTI" (Time To Interactive)
  • Submit PRs describing each change

If your are interested in this improvement, I'd be happy to take ownership of it if you create a small gitcoin bounty.

@AlphaSerpentis
Copy link
Member Author

@AlphaSerpentis I saw your gitcoin posts on the various page re-designs. Spinning up the local web server, I noticed there was a noticeable bottleneck in performance from various dependencies. I'd love to take the time to profile your web pages to identify exactly where this bottleneck is coming from. Here's the steps I would take:

Improving Performance

  • Profile render times (Google Lighthouse tool)
  • Identify which components or dependencies are causing bloat
  • Propose component changes & server side rendering to improve "TTI" (Time To Interactive)
  • Submit PRs describing each change

If your are interested in this improvement, I'd be happy to take ownership of it if you create a small gitcoin bounty.

Heya!

Thanks for stopping by and giving some pointers. We're actually planning to rewrite the website entirely from the ground-up soon which may or may not help in terms of performance, but helps with trying to make our frontend code easier to read and work with for future contributors. If we spot performance issues still, I'll def. consider providing a Gitcoin bounty on this

@tylerferrara
Copy link

@AlphaSerpentis I saw your gitcoin posts on the various page re-designs. Spinning up the local web server, I noticed there was a noticeable bottleneck in performance from various dependencies. I'd love to take the time to profile your web pages to identify exactly where this bottleneck is coming from. Here's the steps I would take:

Improving Performance

  • Profile render times (Google Lighthouse tool)
  • Identify which components or dependencies are causing bloat
  • Propose component changes & server side rendering to improve "TTI" (Time To Interactive)
  • Submit PRs describing each change

If your are interested in this improvement, I'd be happy to take ownership of it if you create a small gitcoin bounty.

Heya!

Thanks for stopping by and giving some pointers. We're actually planning to rewrite the website entirely from the ground-up soon which may or may not help in terms of performance, but helps with trying to make our frontend code easier to read and work with for future contributors. If we spot performance issues still, I'll def. consider providing a Gitcoin bounty on this

Awesome! Thanks for getting back to me so quickly 🙏
If you could recommend any issues or bugs to tackle, I'd be happy to contribute and familiarize myself with your codebase for future gitcoin bounties.

@AlphaSerpentis
Copy link
Member Author

AlphaSerpentis commented Nov 23, 2021

@AlphaSerpentis I saw your gitcoin posts on the various page re-designs. Spinning up the local web server, I noticed there was a noticeable bottleneck in performance from various dependencies. I'd love to take the time to profile your web pages to identify exactly where this bottleneck is coming from. Here's the steps I would take:

Improving Performance

  • Profile render times (Google Lighthouse tool)
  • Identify which components or dependencies are causing bloat
  • Propose component changes & server side rendering to improve "TTI" (Time To Interactive)
  • Submit PRs describing each change

If your are interested in this improvement, I'd be happy to take ownership of it if you create a small gitcoin bounty.

Heya!
Thanks for stopping by and giving some pointers. We're actually planning to rewrite the website entirely from the ground-up soon which may or may not help in terms of performance, but helps with trying to make our frontend code easier to read and work with for future contributors. If we spot performance issues still, I'll def. consider providing a Gitcoin bounty on this

Awesome! Thanks for getting back to me so quickly 🙏 If you could recommend any issues or bugs to tackle, I'd be happy to contribute and familiarize myself with your codebase for future gitcoin bounties.

No worries!

If you're looking for frontend stuff, we're currently in the process of the aforementioned redesign and rewrite, so I would maybe wait until that code is pulled into this repo and decently fleshed out.

I might be looking for someone familiar with ethers.js (or web3.js) since frontend is not my cup of tea, so in the future to plug the components with the web3 libraries when the redesign is complete.

If you're into Solidity, v0.2 (our Venus upgrade) branch has the updated contracts that you could look through, but I'm already in the process of writing v0.3 (Earth upgrade) at its most basic framework to experiment and test with. We haven't deployed v0.2 on any prod. network due to financial constraints and technical constraints (ETH L1 too expensive, Arbitrum having timestamp inaccuracies which prevents AirSwap from operating which we depend on)

If you'd like to remain communications with us, feel free to join https://discord.optional.finance

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants