From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Analysis of redisplay performance on Windows Date: Mon, 28 Jul 2008 01:03:50 -0400 Message-ID: <87fxpueh1l.fsf@stupidchicken.com> References: <87od4kuis1.fsf@stupidchicken.com> <488C45FF.2040509@gnu.org> <87tzebnizu.fsf@stupidchicken.com> <488CE8F6.5080001@gnu.org> <87iqurhupv.fsf@stupidchicken.com> <488CEE6B.6020600@gnu.org> <8763qqiz6j.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1217221459 12963 80.91.229.12 (28 Jul 2008 05:04:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Jul 2008 05:04:19 +0000 (UTC) Cc: Adrian Robert , emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 28 07:05:04 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KNKus-0006XR-2v for ged-emacs-devel@m.gmane.org; Mon, 28 Jul 2008 07:05:03 +0200 Original-Received: from localhost ([127.0.0.1]:57684 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNKtx-0001IK-GA for ged-emacs-devel@m.gmane.org; Mon, 28 Jul 2008 01:04:05 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KNKtr-0001IA-Bu for emacs-devel@gnu.org; Mon, 28 Jul 2008 01:03:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KNKto-0001Ht-Lp for emacs-devel@gnu.org; Mon, 28 Jul 2008 01:03:57 -0400 Original-Received: from [199.232.76.173] (port=34468 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNKto-0001Hg-5r for emacs-devel@gnu.org; Mon, 28 Jul 2008 01:03:56 -0400 Original-Received: from c-24-63-201-57.hsd1.ma.comcast.net ([24.63.201.57]:21088 helo=furry) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KNKtn-0008U4-KS for emacs-devel@gnu.org; Mon, 28 Jul 2008 01:03:55 -0400 Original-Received: by furry (Postfix, from userid 1000) id 0558EC059; Mon, 28 Jul 2008 01:03:51 -0400 (EDT) In-Reply-To: (Adrian Robert's message of "Mon, 28 Jul 2008 03:06:16 +0000 (UTC)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101624 Archived-At: Adrian Robert writes: > In the NS font driver (nsfont.m) these two functions cache info for > each font by block of 256 (stored in nsfont_info -- nsterm.h). This > made a significant different in rendering speed when I implemented it, > and the memory cost is not high unless lots of different char ranges > are being rendered in lots of different fonts. Moving this code up to > font.c would be another option to consider. If we go this route, it's probably faster to reimplement this cache separately for w32, using the NS code as a guide and keeping it as close as possible. Working with the platform-independent code, you'd have to worry about screwing things up on other platforms. We can always consolidate/refactor the code in the next development cycle. Handa, do you have any comments about the nsfont_info mechanism that Adrian pointed to?