I have used JabRef for many years on Ubuntu, Debian and Windows 7. However, I am experiencing very slow startups on my new Windows 10 machine. This is an i7 processor with 16GB of RAM and an SSD but still takes about 5 minutes to start JabRef. I have tried the new development build, 4.3.1 and 3.8.2 and all have the same problem.
Please could somebody advise on what I can do to make JabRef usable again?
This depends on several factors., The size of the last opened database and we recently had issues with the telemtetry collection library. Check if you have it enabled,
I don’t believe that I have the telemtetry collection library enabled (please advise where the option is for this). Currently I have 3.8.2 installed as this was the most stable version I was running on Windows 7.
JabRef is still slow even when there is no last opened database (i.e. opening blank).
Is there some configuration file that needs editing to speed up the load and response time?
Is there any update on this?
The slow starting is really making JabRef unusable for me.
JabRef normally does not takes more than a few seconds to start. Thus, I suspect there is a problem on your side/your configuration of JabRef. Do you load JabRef from a network drive? Can you try to run it from the console as described here: http://help.jabref.org/en/CommandLine.
Moreover, the most recent development version contains some general preformance improvements, which may (or may not) fix the issues you experience. You can try it out from https://builds.jabref.org/master/, but please make a backup of your data before.
I noticed this as well and found that the loading of the last used libraries blocks the rest of JabRef.
I already experimented a bit to load the libraries in the background and in parallel.
Currently work in progess. You can follow that PR.