I am already using ureadahead and preload for a long time. It works fine, but I often have to use Microsoft Office 2010, which is installed with PlayOnLinux. The first load of Word, Excel or Powerpoint needs a long time. The second load time of these applications is okay.
So I am wondering if there is the possibility to preload these applications? Can anybody help me how to do this?
I found out that there is also a "wine-preloader", but I couldn't find out how it can help me in this case exactly. It's also a little bit confusing to me if the first longer load time is because of PlayOnLinux' virtual machine or because of Wine's loading of the specific application.
So my explicit questions are:
- What exactly and how can I preload anything to speed up the first start of the Office Applications?
- Can I keep the preloading, also if there is a longer idle time of not using the office applications? (to avoid that there is i.e. 60 minutes later a behaviour like the "first load" again)
- Of course I am thankful for other tipps as well. Please avoid instructing me to use Libre- or OpenOffice. I know :) But this is not the topic here.
Thanks a lot!
Regards, Berzi
There is a configuration option for
/etc/preload.conf
calledmapprefix
that defaults to this:This means that by default files in
/usr
,/lib
and/var/cache
are eligible, but other files won't be preloaded. You could modify it to include the path on disk where your program you want cached exists, such as:Where
/home/someone/.winexxx
is theWINE_PREFIX
for the given PlayOnLinux program.Another option would be to use the
gopreload
command and run that program manually, something like this:Although for that a.) you would need to compile/install
gopreload
manually and b.) you should need to ensure you're running the correctwine
program with the prefix and other settings PlayOnLinux would use. You can likely get those by looking at a shortcut or .desktop file if you can get PlayOnLinux to create one for you.However, there is another problem which is what preload considers code versus data and how it preloads things. I have a feeling that most of what is being executed by wine will end up being seen as data and not preloaded. You'll want to check the preload log files to see what it's actually doing if you go that route.
A poor man's solution could be to create a boot-script that simply reads these files from disk thus "priming" the cache to contain them, something like:
ionice -c 3 vmtouch '/home/someone/.winexxx/drive_c/Program Files (x86)/Microsoft Office'
This would run
ionice
so that it happens in the background / idle not to slow down other functionality and thenvmtouch
to map the data for the program into RAM.