Is there a way to speed up the Dash? When I press the super key for the first time it can take ~2 seconds for the dash to appear. Whereas if I use Synapse, it will appear instantly.
I. Install Unsettings. Type in terminal
Open Unsettings. You can try 2 changes.
II. Install the Compiz Config Settings Manager. Type in terminal
Open the compiz manager. Go to OpenGL and select Texture Filter > Fast
Remember to log out!
Deactivating the "blur" effect might help.
To do so install "MyUnity" in the Ubuntu Software Center. Then you can disable the blur effect by setting the "Blur" option on the "dash"-tab to "Off".
Unity Dash in Ubuntu 12.04LTS (Unity 5) may lack the swiftness and fluidity of later Unity versions like Ubuntu 14.04LTS's Unity 7, but it's stable enough for everyday use. Before you try the steps for improving Unity's speed, it's recommended to update Unity and Compiz to their latest versions available on Ubuntu 12.04LTS's repositories. This is because initial versions of Unity 5 had stability problems, but later ones received stability and speed improvements backported from successive Ubuntu releases. By the time final release of Ubuntu 12.04LTS (12.04.5) was out, Unity (v5.20) had gotten quite solid and stable.
Some of the steps suggested here require Compiz Config. You can also use other tools like MyUnity, Unsettings, Ubuntu Tweak or editing the schema/settings directly through dconf-editor or gsettings. But, I recommend Compiz Config, coz it allows you to edit all Compiz and Unity settings in one place. Click here to install Compiz Config
Step 1: Deactivate Dynamic Blur: This would reduce lag and stutter experienced when using Dash. Open Compiz Config -> Ubuntu Unity Plugin -> Experimental Tab -> Dash Blur and change it to Static Blur or No Blur.
Step 2: Remove unwanted Lens and Scopes: The Dash in Ubuntu 14.04LTS provides an option to disable/enable Scopes. Unfortunately, this feature isn't available in 12.04LTS's Unity. However, they can still be manually disabled by editing each individual lens' setting under dconf-editor->desktop->unity->lenses. But, I prefer to remove the unwanted Lens and Scopes altogether.
Step 3: Reduce Dash Startup Delay: You might have noticed that Dash takes a long time to load when used for the first time after booting. This startup delay can be reduced by using preload or similar daemons. Click here to install preload
Step 4: Reduce Graphics Settings: If all the previous steps didn't improve speed noticeably, or if you are still hungry for more performance, reduce the Graphics Settings for Compiz. I got this idea from Ed Villegas' Answer for Ubuntu 12.10. But remember, this change affects graphics quality of the entire Ubuntu system, not just Unity alone! Open Compiz Config->OpenGL->Texture Filter and set it to Fast.
After doing all the above restart the system before checking the results, or else Unity may behave abnormally.
Note that Ubuntu 12.04LTS's Unity 5 doesn't have a Low Graphics Mode like that of Unity 7 on Ubuntu 14.04LTS. However, 12.04LTS provides a similar looking but very different Unity2D desktop, which runs on a different Window Manager instead of Compiz. You may use it if your graphics hardware is very weak. But, I wouldn't recommend using it under normal cases.
There may not be anything to do for that.
If the Dash hasn't been used for a while, it is possible its code has been evicted from memory to make room for something else used recently. If that is the case it has to grab that back from disk before it is able to act.
Again, there may not be a workaround that would solve it without adding some other slowdown because of memory usage manipulation.
The dash is slow due to the extra high end graphics which your graphics card supports with much difficulty. Add the following line to the
The above line will enable low graphics mode which can be easily supported by your GPU. Dont worry you will not loose any image quality in case you are fearing so :)
And save it and logoff and login again. And now check. Your Dash home would work fast and smooth.
There are at least two bugs reported for this long-standing problem (goes back to 2012). Please consider adding yourselves to the bugs to bump the matter as there seems not to be much attention paid to it from the developers: