Skip to content

Performance optimizations - Internalize after request #18

@tabacitu

Description

@tabacitu

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;

Metadata

Metadata

Assignees

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions