You are not logged in.
It usually takes several tens of seconds for acroread to open up for me. Once its been opened and then closed and I open it again, it only takes a couple of seconds (ie: in memory). Is there any reason it would take so long the first time, something I can speed up? Its not that huge and ungainly a program that it should take so long on a processor this speed. It also doesn't seem to be an IO problem because my disk monitors don't spike while waiting for the pig to open. The only thing I could think of was perhaps its making a network access before opening (adobe spyware??), but this seems unlikely... and even if it was happening, it shouldn't take that long because I have a hell of a good internet connection too.
I suppose maybe its because its distributed as a binary... not i686 like I'm used to. Could be that.
Ok, but for the ranting -- does anybody have any ideas how I can speed the bloody thing up? Its really annoying when I happen to click a pdf link in firefox and the whole browser freezes for more than half a minute while acroread is checking itself in the mirror...
Dusty
Offline
I've noticed the same thing. Bloody annoying. Unfortunately I've no idea how to remedy it..
Offline
I seem to remember that there was a lot of fuss about acrobat performance for all platforms and it had something to do with plugin loading. I recall someone writing a guide about removing a load of plugins that are unlikely to be used and that improved things a lot.
I'm sorry, but I don't have any specifics. I agree that the freezing in firefox is very annoying. I really ought to investigate myself...
Offline
I think it has something to do with a font cache file acrobat tries to read at startup. There was a discussion about this on the gentoo forums a few months ago.
On my system the file is ~/.adobe/Acrobat/7.0/Cache/UnixFnt07.lst.
The suggested workaround was to add the following to the startup binary
/usr/bin/acroread:
rm ~/.adobe/Acrobat/7.0/Cache/UnixFnt07.lst
I'm not sure what the sideffects are, but I haven't noticed any yet.
-w
Offline
does anybody have any ideas how I can speed the bloody thing up?
sorry to piss on the parade, but why not use xpdf? takes about 1 second to open can search, zoom, change page. I haven't really used any additional functionnalities from acroread but would be curious what they are (especially since it's not even the professional version) to justify that absolutely obscene load time.
Offline
Does xpdf has a firefox plugin?
I think after adding that rm line acroread starts faster.
EDIT: hmm, no, it doesn't start faster it was only once.
Offline
Dusty wrote:does anybody have any ideas how I can speed the bloody thing up?
sorry to piss on the parade, but why not use xpdf?
I used to flip between it and kpdf, but neither of them supports enough of the many pdfs I have to read. I'm not sure what's special about them, but I'm looking at literally dozens of papers per week, and at least half of them don't seem to render properly in the open source alternatives to acroread. I haven't tried them in a while though, perhaps they work better.
Dusty
Offline
I see what you mean. Well I must look at about 20-25 pdfs a week and it all shows up fine. Admittedly they're pretty much all from the same kind of sources. Give it a try anyway, you'll loose about 2 minutes if doesn't work
Ciao
Offline
Is it possible that it has something to do with the fact that it's statically linked to the gtk+ libs? Opera, which is statically linked to qt, doesn't start fast either (as opposed to other qt/kde apps).
Being able to read someone else's code is a *good thing*. Not a fundamental right.
Offline
it is because of the plugins! disable the plugins you do not need by renaming them. you find the plugins in /opt/acrobat/Reader/intellinux/plug_ins/.
sorry for my bad english
Offline
Whoa, I moved the plug_ins directory to pplug_ins, and it launches in under a second.
Offline
I left the plugins alone and did what wrj said and the performance increase is great too.
Dusty
Offline