caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Weak hashtables & aggressive caching
Date: Tue, 15 Aug 2006 10:17:08 -0600	[thread overview]
Message-ID: <44E1F384.7080304@gushee.net> (raw)
In-Reply-To: <1155617756.29241.25.camel@rosella.wigram>

skaller wrote:

>> I wonder how you trigger the GC, to both keep the cache long enough,
>> and to avoid filling the memory too much, and resulting in lots of
>> swapping.
> 
> I'm confused. First, a pixmap doesn't have any pointers in it,
> so it doesn't need to be scanned by the GC.

Does that statement apply to a GdkPixbuf.pixbuf? That is the type I am 
using.

I took Jacques' statement to mean that LablGTK was explicitly invoking 
the GC--though of course I'd like to hear his answer on that point.

> Second, you'd need a LOT of images to come even close
> to running out of address space (on a 64 bit machine anyhow :)

:) Of course, many people are still using those antiquated 32-bit 
processors. I know that real software developers use overpowered 
machines to help insulate them from the constraints that face ordinary 
users. Me, I can't afford a powerful computer, so I guess I'm not a real 
developer.

> I have thousands of images and I can scan them at full size
> very fast with GQView .. I can only barely see the drawing
> happen .. it almost keeps up with the keyboard repeat rate
> at full screen size .. and that includes *scaling* the images.
> Mind you .. GQView is extremely quick

Interesting. For me it's neither fast nor slow.

> and it knows when to move on
> (interrupts rendering when you tell it to view a new image).

That's good. I would like to know (or figure out) how to do that with 
LablGTK.

> Lets get real here: the difficulties arise editing video,
> not still pictures.

Except for those of us with really old hardware. I imagine there are a 
lot of such folks in Africa; and seeing as America is rapidly becoming a 
Third World country, maybe more then you'd expect here.

-- 
Matt Gushee
: Bantam - lightweight file manager : matt.gushee.net/software/bantam/ :
: RASCL's A Simple Configuration Language :     matt.gushee.net/rascl/ :


      reply	other threads:[~2006-08-15 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 14:58 Matt Gushee
2006-08-14 15:47 ` [Caml-list] " Richard Jones
2006-08-14 16:28   ` Matt Gushee
     [not found]     ` <44E0A8F1.8060504@janestcapital.com>
2006-08-14 17:35       ` Matt Gushee
2006-08-14 18:18     ` Richard Jones
2006-08-14 23:25       ` Matt Gushee
2006-08-14 21:23 ` Jacques Garrigue
2006-08-14 23:30   ` Matt Gushee
2006-08-16  0:54     ` Jacques Garrigue
2006-08-16  4:33       ` Matt Gushee
2006-08-15  4:55   ` skaller
2006-08-15 16:17     ` Matt Gushee [this message]

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=44E1F384.7080304@gushee.net \
    --to=matt@gushee.net \
    --cc=caml-list@inria.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).