From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Remote display-time-mail-file Date: Sat, 18 Sep 2010 12:49:37 +0200 Message-ID: <8762y39vi6.fsf@gmx.de> References: <837hil355j.fsf@gnu.org> <83zkvh1m4j.fsf@gnu.org> <87pqwdbdxs.fsf@gmx.de> <83r5gs1th2.fsf@gnu.org> <87ocbwnmkz.fsf@gmx.de> <87aangnl1j.fsf@gmx.de> <83sk18yrj6.fsf@gnu.org> <83r5grzaei.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1284807046 24028 80.91.229.12 (18 Sep 2010 10:50:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 18 Sep 2010 10:50:46 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 18 12:50:44 2010 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.69) (envelope-from ) id 1Owv08-0005vf-RE for ged-emacs-devel@m.gmane.org; Sat, 18 Sep 2010 12:50:40 +0200 Original-Received: from localhost ([127.0.0.1]:51065 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Owv04-00059n-Lt for ged-emacs-devel@m.gmane.org; Sat, 18 Sep 2010 06:50:32 -0400 Original-Received: from [140.186.70.92] (port=49705 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Owuzw-0004wk-P7 for emacs-devel@gnu.org; Sat, 18 Sep 2010 06:50:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OwuzF-0004Gs-Di for emacs-devel@gnu.org; Sat, 18 Sep 2010 06:49:42 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:52205 helo=mail.gmx.net) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OwuzF-0004Gf-2u for emacs-devel@gnu.org; Sat, 18 Sep 2010 06:49:41 -0400 Original-Received: (qmail invoked by alias); 18 Sep 2010 10:49:38 -0000 Original-Received: from p4FC194ED.dip0.t-ipconnect.de (EHLO arthur.gmx.de) [79.193.148.237] by mail.gmx.net (mp025) with SMTP; 18 Sep 2010 12:49:38 +0200 X-Authenticated: #3708877 X-Provags-ID: V01U2FsdGVkX1/aETNQifvawbJ47Lw2O6SBhIAvjWE7I7q7rtNoR1 qKVVAaL7F2sSoA In-Reply-To: <83r5grzaei.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Sep 2010 11:08:37 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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:130390 Archived-At: Eli Zaretskii writes: > That's true, but my conclusion from this is different: we probably > should have finer granularity of the cache setting. > > I guess some of the internal Tramp functions need not be called any > time soon after the first call, for example those that find out which > method to use to access the remote and which scripts to run on the > remote side. Other internal functions will need to run every time > display-time-file-nonempty-p is called. And there could be those in > between. So perhaps these internal functions should be categorized in > some reasonable manner, and then corresponding values added to the > repertoire of tramp-cache-inhibit-cache's values, so that Lisp > programs could have finer control on what is being cached and when the > cache is refreshed. When I have started with Tramp 2.1, 5 years ago, I did some profiling with Tramp. IIRC, there are only some few functions (like file-attributes), which are called frequently, and which profit from caching more than other functions. Maybe we shall rerun this profiling again, since we have started Tramp 2.2 :-) I guess we could use caching just for these high-runner functions; for the other ones it doesn't matter whether we have caching, or not. Best regards, Michael.