Delivered-To: garrigue at math.nagoya-u.ac.jp
Authentication-Results: mailhost.math.nagoya-u.ac.jp sender=lablgtk-bounces at yquem.inria.fr; domainkey=neutral (no query protocol specified; no policy for yquem.inria.fr)
Delivered-To: lablgtk at yquem.inria.fr
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:sender:received
	:in-reply-to:references:date:x-google-sender-auth:message-id:subject
	:from:to:cc:content-type;
	bh=DNfx+cPOKzXpcKjlkcZGGEMw7+zMab7ByyF1u6oGw+4=;
	b=qI1qu+Bb/5jToK0uR8Q5w4R7BwItqvIGYxuKASSZS9i+JRtxyzEar18LTrKq/gCsN/
	nzs9Qw76mablmQjHan1Eg/O1CLlBUiOYf0cErK/BCEpM4HSDaGxCgpl5WOx/5W00W9lX
	d7ewYn3v+2L107Kzi4De57BkR24/vWAucn7pU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	b=o4k7DqHqRkv1amEKMHHiixPJLGyH1w0lzL7z8RMEOMxYAd5n1o6EW4Ilxk7c+rDXaD
	oReZymO2bJLO1AEFv0xulJABn2vJoorXfrixw5rqXPGlfLX8eX7KXRO/dTM5GZI+Ashm
	/YYK7Rfy2F+V1RJAKOpmGV0q0k8LEIwuqTy+k=
MIME-Version: 1.0
In-Reply-To: <20101215074302.51916f2e at alcazar>
References: <20101214083626.59faf109 at alcazar> <20101214084959.0c5ce2ef at alcazar>
	<AANLkTi=1e1ve590e+6adrANNtbY0t9hSyz-YvELtAZQN@mail.gmail.com>
	<20101215074302.51916f2e@alcazar>
Date: Wed, 15 Dec 2010 16:24:17 +0900
Message-ID: <AANLkTim8KA0dG_dV5-DxrSwf8anKpFJzTPW4UA0U6K2f at mail.gmail.com>
Subject: Re: [Lablgtk] CPU consumption with GtkThread
From: Jacques Garrigue <garrigue at math.nagoya-u.ac.jp>
To: Maxence Guesdon <Maxence.Guesdon at inria.fr>
Content-Type: text/plain; charset=ISO-8859-1
Cc: lablgtk at yquem.inria.fr
Status: U

On Wed, Dec 15, 2010 at 3:43 PM, Maxence Guesdon
<Maxence.Guesdon@inria.fr> wrote:
> On Tue, 14 Dec 2010 12:18:00 +0100
> Adrien <camaradetux@gmail.com> wrote:
>
>> Hi,
>>
>> I actually made it adaptive later on[1]. The drawback was that
>> animations could take more time to update. The adaptative version
>> worked quite well but reducing the delay wasn't instantaneous. It was
>> pretty dumb and experimental, I could probably put more thought in it
>> if needed.
>> One of my test was using the acid3 test[2]. Basically, each step of
>> the animation required one iteration of the loop. So depending on your
>> uses it might or might not be a good idea.
>
> Maybe the GtkThread module could allow setting some kind of callback so
> that the application could change this delay when needed ?

I was not aware of this GtkThread problem, but I'm certainly not opposed to
making the delay tweakable by the application. One difficulty is that I suppose
this depends quite a lot on the OS scheduler, and in particular on its
granularity,
so that the application may not know enough to set this value properly, but at
least it is better than nothing.

  Jacques

_______________________________________________
Lablgtk mailing list
Lablgtk@yquem.inria.fr
http://yquem.inria.fr/cgi-bin/mailman/listinfo/lablgtk