Pre-Cache Application Menu

[eccentricexit]

There is a seconds long delay for opening the applications finder for the first time (after logging in).

This is different from #47 as it is not a lag when moving between pages, but for openning the view in the first place

Information:

• Juno
• Disk hard drive
• I have a dual boot and no hibernation
• 23 apps (2 pages worth of apps)

Perhaps it is possible to cache this in the background so it is fast when opening it the first time? :zap:

[peteruithoven]

One aspect of why it takes so long might also be that it (partly) initializes a lot of system settings plugs, to enable searching through them. The icons themselves are loaded async, so that shouldn't impact the time to first open.

[megatux]

I see. Are plugs loading async, too? I find them a bit like bloat, e.g. the calculator. The one that matches with an executable is ok, but most of the time I want the output in a console, so very little use. I would like the Apps menu to keep focus only on launching GUI apps. The one that matches from settings "pages" is ok, but should not be in detriment of speeding launching "normal" apps. If we decide to implement some caching for the menu apps, do we know approx. the memory usage for a sample like the above?

[eccentricexit]

One aspect of why it takes so long might also be that it (partly) initializes a lot of system settings plugs, to enable searching through them.

Perhaps this could be moved to the system initialization or somewhere else so it doesn't start when the user opens the Application Menu.

[ghost]

Pre-cashe would allow for faster load times, but after switching to a SDD load times are faster default.

[eccentricexit]

I suppose it would come down to the evaluating how much effort it would take to code that, % of people that use eOS and don't have SSD + adoption rate.

[sprite-1]

In the meantime, I just added a script on startup like this

wingpanel -t app-launcher
sleep 1
xdotool keydown Super key space keyup Super

[janxkoci]

I see this exact issue on small netbook with low-spec Celeron processor and eMMC disk, but it's not really noticeable on another laptop with i5 and SSD. I suspected it's the processor or RAM, never thought of the drive causing the slowdown 😮