On Sat, Jan 30, 2010 at 4:56 PM, JohnS <jses27@gmail.com> wrote:
>
>> This only happens during the first load in a while - probably until
>> the cache for its pages clear, or it may be going out on the web to
>> check for updates, though this seems to take a long time.
>
> Check the settings for adobe because honestly I had to change mine!
> the cache settings i think for adobe reading pages ahead into memory.
>

I wondered about that, but:

1) I haven't been able to find a setting for that in the 8+ versions of AR, and

2) this was a 2-page document - how could it be dead for 22 seconds
just to read ahead one page?

mhr
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

MHR wrote:
> On Sat, Jan 30, 2010 at 4:56 PM, JohnS <jses27@gmail.com> wrote:
>>> This only happens during the first load in a while - probably until
>>> the cache for its pages clear, or it may be going out on the web to
>>> check for updates, though this seems to take a long time.
>> Check the settings for adobe because honestly I had to change mine!
>> the cache settings i think for adobe reading pages ahead into memory.
>>
>
> I wondered about that, but:
>
> 1) I haven't been able to find a setting for that in the 8+ versions of AR, and
>
> 2) this was a 2-page document - how could it be dead for 22 seconds
> just to read ahead one page?

Put a network sniffer on it. That may be when it calls home to check for
updates.

Bob McConnell
N2SPP
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Sat, 2010-01-30 at 18:38 -0800, MHR wrote:
> On Sat, Jan 30, 2010 at 4:56 PM, JohnS <jses27@gmail.com> wrote:
> >
> >> This only happens during the first load in a while - probably until
> >> the cache for its pages clear, or it may be going out on the web to
> >> check for updates, though this seems to take a long time.
> >
> > Check the settings for adobe because honestly I had to change mine!
> > the cache settings i think for adobe reading pages ahead into memory.
> >
>
> I wondered about that, but:
>
> 1) I haven't been able to find a setting for that in the 8+ versions of AR, and
>
> 2) this was a 2-page document - how could it be dead for 22 seconds
> just to read ahead one page?
---
Look for Edit | Preferences | Reading | Screen Reader Options: Select
For Large Documents only read the currently visible pages

Min number of pages in a large doc; 10

Those are what I had to change. If I open Red Hat Enterprise Deployment
Guide.pdf from redhat.com it takes 5 secs for the whole PDF to load.
That is with it on local disk or net share.

John

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Sat, Jan 30, 2010 at 9:46 PM, JohnS <jses27@gmail.com> wrote:
>
> Look for Edit | Preferences | Reading | Screen Reader Options: Select
> For Large Documents only read the currently visible pages
>
> Min number of pages in a large doc; 10
>

Interesting. Mine was set to 50, but when I changed it to 10, it
loaded Sun's Microsoft Documents to OpenOffice Documents guide in a
jiffy (not literally...) and was paging right away.

Still, I'll have to test that tomorrow - it doesn't make sense that a
2 page document would be so difficult.

mhr
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

MHR wrote:
> I've noticed recently that the latest version of Adobe's Acrobat
> Reader (9.3) has a really annoying tendency to stop for 30-60 seconds
> shortly after it starts up to read/display a PDF file. I don't see
> this on my Windows copies, just on CentOS.

I am on Ubuntu 9.10 AMD64. Same thing also happening here.
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos