Skip to content
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

Performance optimizations - Internalize after request #18

Open
1 of 2 tasks
tabacitu opened this issue Mar 20, 2023 · 1 comment
Open
1 of 2 tasks

Performance optimizations - Internalize after request #18

tabacitu opened this issue Mar 20, 2023 · 1 comment

Comments

@tabacitu
Copy link
Member

tabacitu commented Mar 20, 2023

Let's discover WHAT are out weakest points. Our most expensive operations, and then we decide if we should do anything to speed them up.

Possible improvements we talked about:

  • 1. MUST - generating a MAP of all files that are internalized (.basset file) - might save miliseconds on each page load;

  • 2. SHOULD/COULD - moving the internalization process till AFTER the request has been served (deliver CDN asset to browser, then internalize in the same process, for the next request) - might save entire seconds, but only on first load;

@promatik promatik changed the title Performance optimizations Performance optimizations - Internalize after request Apr 19, 2023
@promatik
Copy link
Contributor

1. generating a MAP of all files that are internalized (.basset file) - might save miliseconds on each page load;

Done with #27 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants