Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
Make some apps (mainly KDE apps with text fields) start faster
Just create a folder "~/.compose-cache".
Or better yet, at least in a semi-philosophical level, have your startup script to create "/dev/shm/.compose-cache" every time, and just create it once, and a soft link to your home folder. No unnecessary access to your disk, writing to and reading from memory instead. Which is often assumed to be better for several cache-type usages, both for performance and (supposedly) for the lifespan of your hard disk*. Some people even make some scripts that will copy the entire profile folder of an application such as firefox or chrome to /dev/shm, where the browser will use it, and synchronize it back to the disk when it is closed.
If the PC is shared by more people who may use it with simultaneous sessions, perhaps it's better to have it as "/dev/shm/$USER/.compose-cache" instead.
* however, some studies surprisingly show no significant correlation between heavy disk usage and decreased lifespan, perhaps even somewhat of an inverse correlation when lower usage is accompanied by lower temperatures, which perhaps even more counter intuitively, correlate more with shorter lifespan than hotter temperatures. I'm not suggesting you should light a fire inside your cabinet though.
Or better yet, at least in a semi-philosophical level, have your startup script to create "/dev/shm/.compose-cache" every time, and just create it once, and a soft link to your home folder. No unnecessary access to your disk, writing to and reading from memory instead. Which is often assumed to be better for several cache-type usages, both for performance and (supposedly) for the lifespan of your hard disk*. Some people even make some scripts that will copy the entire profile folder of an application such as firefox or chrome to /dev/shm, where the browser will use it, and synchronize it back to the disk when it is closed.
If the PC is shared by more people who may use it with simultaneous sessions, perhaps it's better to have it as "/dev/shm/$USER/.compose-cache" instead.
* however, some studies surprisingly show no significant correlation between heavy disk usage and decreased lifespan, perhaps even somewhat of an inverse correlation when lower usage is accompanied by lower temperatures, which perhaps even more counter intuitively, correlate more with shorter lifespan than hotter temperatures. I'm not suggesting you should light a fire inside your cabinet though.
Total Comments 0
