All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Antonio Vargas <wind@cocodriloo.com>
Cc: Tom Sightler <ttsig@tuxyturvy.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] O16.2int
Date: Tue, 19 Aug 2003 09:47:25 +1000	[thread overview]
Message-ID: <200308190947.26139.kernel@kolivas.org> (raw)
In-Reply-To: <20030818165102.GB7570@wind.cocodriloo.com>

On Tue, 19 Aug 2003 02:51, Antonio Vargas wrote:
> On Mon, Aug 18, 2003 at 11:21:04AM +1000, Con Kolivas wrote:
> > Quoting Tom Sightler <ttsig@tuxyturvy.com>:
> > > 2. -- Adobe Acrobat 5.07 for Linux seems to have a very similar issue,
> > > a large complex document seems to starve out the whole system making
> > > the system feel locked up for several seconds.
> >
> > Actually I've profiled acroread and it seems to be more a memory issue
> > than a scheduler one per se. Something very inefficient about it's design
> > and it behaves much worse as a mozilla plugin than standalone. Give it
> > lots of cpu time and it just keeps doing more and more vm work.
>
> Acrobat has a switch so that it keeps a cache of rendered pages, and
> obviously it default to ON, so just reading a big PDF file page by
> page will trash all the system with lots useless data. BUT, for simple
> PDF usage in a non-multitasking single-user machine it's faster
> so there you have a possible reason for it's strange behaviour.

Yes. As well as this though, there is a specific problem with it as a mozilla 
plugin. Profiling shows some libgdk is doing all the work and it really 
behaves badly. Put the same plugin into a different browser (eg opera) and it 
behaves well, working pretty much like standalone acroread. 

Con


  reply	other threads:[~2003-08-18 23:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 20:37 [PATCH] O16.2int Benjamin Weber
2003-08-17 21:47 ` Tom Sightler
2003-08-18  1:21   ` Con Kolivas
2003-08-18 16:51     ` Antonio Vargas
2003-08-18 23:47       ` Con Kolivas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-16 11:07 Voluspa
2003-08-16 14:09 ` Con Kolivas
2003-08-16 14:41   ` Nick Piggin
2003-08-16 15:00     ` Con Kolivas
2003-08-16 14:44   ` Voluspa
2003-08-16  9:02 Con Kolivas
2003-08-16 13:29 ` Wiktor Wodecki
2003-08-17  7:40 ` Andrew Morton
2003-08-17  9:30   ` Con Kolivas
2003-08-17 14:59   ` Con Kolivas
2003-08-17 21:06     ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200308190947.26139.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttsig@tuxyturvy.com \
    --cc=wind@cocodriloo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.