Skip to content

Remove async loading from merge request's File Tree

What does this MR do and why?

This MR removes:

  1. File Tree worker which is adding unnecessary overhead to the file tree data processing. Processing this data on the main thread does not introduce a significant thread blocking (the whole task takes less than 30 μs, image).
  2. Virtual scrolling components async loading. Loading these components asynchronously increases bundle size and loading times because of waterfall effect (we have to load the app before we start fetching these components).

Screenshots or screen recordings

Sitespeed performance comparison

image

(left if old, right is new)

How to set up and validate locally

  1. Open any merge request Changes page

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports