With each new version the library becomes larger in size and the execution time of the load event increases. Are there any plans to reduce the speed of the "load" event?

[Vin4er]

Hello!
Our application is chasing the rendering speed. Before each update of any library, we check every time whether this library will make our application worse, and whether it will handle more traffic.
We use our own tile vector geoserver, styles are described on mbstyle.

We look at such indicators

1. library size
2. Time from map creation to the implementation of "load" events at the time of the map.

When we started using maplibre-gl 1.14.0.
Weight 767kb
The time of "load" events does not reach 230ms.
Usually within 188-215ms

Then, after some time, we updated to 2.1.9, having measured the loading speed/weight of the library before that. It became 60kb lighter, and the speed of implementation of "load" events of the map practically did not change.
Weight 706kb
The time of "load" events does not reach 231ms.
Usually within 200-215ms

Then, wanting to update to version 3.x.x, I noticed that the library again weighed 60 KB more, and the time from creating the map increased.

Compared several versions of libraries. Made 5 measurements, on triggering the "load" event, 5 different major versions of libraries.

Measurements are taken like this:

<script>
    console.time('Map ready (load event)');
    const map = new maplibregl.Map({
        container: 'map',
        style:  './mb-global.mbstyle.json',
        center: [60, 58],
        zoom: 4
    });
    map.on('load', () => {
        console.timeEnd('Map ready (load event)')
    });
</script>

// maplibre-1.4.0 **Size: 767kb**
maplibre140.html:32 Map ready (load event): 230.884033203125 ms
maplibre140.html:32 Map ready (load event): 195.416015625 ms
maplibre140.html:32 Map ready (load event): **234.468994140625** ms
maplibre140.html:32 Map ready (load event): 222.37109375 ms
maplibre140.html:32 Map ready (load event): 188.225830078125 ms

// maplibre-2.1.9 **Size: 706kb**
maplibre219.html:166 Map ready (load event): **231.14501953125** ms
maplibre219.html:166 Map ready (load event): 229.693115234375 ms
maplibre219.html:166 Map ready (load event): 200.72802734375 ms
maplibre219.html:166 Map ready (load event): 206.010986328125 ms
maplibre219.html:166 Map ready (load event): 196.467041015625 ms

// maplibre-3.1.0 **Size: 761kb**
maplibre310.html:166 Map ready (load event): **281.111083984375** ms
maplibre310.html:166 Map ready (load event): 258.56298828125 ms
maplibre310.html:166 Map ready (load event): 272.616943359375 ms
maplibre310.html:166 Map ready (load event): 262.794921875 ms
maplibre310.html:166 Map ready (load event): 273.0869140625 ms

// maplibre-4.1.0 **Size: 775kb**
maplibre410.html:166 Map ready (load event): 295.2021484375 ms
maplibre410.html:166 Map ready (load event): 280.302001953125 ms
maplibre410.html:166 Map ready (load event): 277.304931640625 ms
maplibre410.html:166 Map ready (load event): 269.91015625 ms
maplibre410.html:166 Map ready (load event): **295.973876953125** ms
 
// maplibre-5.1.1 **Size: 910kb**
maplibre511.html:166 Map ready (load event): **383.303955078125** ms
maplibre511.html:166 Map ready (load event): 289.19091796875 ms
maplibre511.html:166 Map ready (load event): 341.06494140625 ms
maplibre511.html:166 Map ready (load event): 311.5810546875 ms
maplibre511.html:166 Map ready (load event): 324.840087890625 ms

Is it planned to reduce the speed of the "load" event (very important), and work to reduce the weight of the library? (can be tolerated)

I want to use new versions of the library, but I have no right to worsen the application.

[HarelM]

If this is something you would like to pursue then by all means, be my guest.
I have all kinds of ideas how to split the library to smaller components and keep the current package as an uber package of all the components.
But it is a huge undertake and requires an investment of someone/some company who will champion this.
I, unfortunately, do not have the capacity to do so.

In general, our direction is focus around new features and less about time it takes to load this library as we assume internet speed and computation will only grow over time.

[HarelM]

I think this is somewhat of a duplicate of the following issue, and maybe other issues

• Tree shaking #977