unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Moore, Rider" <rmoore@cooley.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "67672@debbugs.gnu.org" <67672@debbugs.gnu.org>,
	"Chand, Suresh" <schand@cooley.com>
Subject: bug#67672: EMACS - Slow opening files
Date: Tue, 12 Dec 2023 17:57:56 +0000	[thread overview]
Message-ID: <CY8PR11MB71335EED101F6E673DD013A1AE8EA@CY8PR11MB7133.namprd11.prod.outlook.com> (raw)
In-Reply-To: <83il53tkn4.fsf@gnu.org>

Eli,

For the purpose of our business we only want to use Emacs as a text editor.  We are working with very large mercurial and git repositories under version control.  If files are under version control, is Emacs doing anything extra besides opening them as a normal text editor would?

Thanks,

-Rider

-----Original Message-----
From: Eli Zaretskii <eliz@gnu.org>
Sent: Tuesday, December 12, 2023 9:07 AM
To: Moore, Rider <rmoore@cooley.com>
Cc: Chand, Suresh <schand@cooley.com>; 67672@debbugs.gnu.org
Subject: Re: bug#67672: EMACS - Slow opening files

[External]

______________________________________________________________________
> From: "Moore, Rider" <rmoore@cooley.com>
> CC: "Chand, Suresh" <schand@cooley.com>,
>         "67672@debbugs.gnu.org"
>       <67672@debbugs.gnu.org>
> Date: Tue, 12 Dec 2023 15:52:53 +0000
>
> The delay is only present for files located within the Truecrypt volume we are using (essential for our purposes).

OK, this is good to know, thanks.

> Do you know of any commands or settings adjustments needed when working with a Emacs and a Truecrypt volume?

No, I don't.  I don't think we have ever heard about problems with these particular volumes.  Which is why I suggested to run this slow operation under perf, which will allow you to produce a profile of the code, and hopefully will show us which part of the code is the bottleneck.  I don't think we can make any progress here unless we understand which parts of the code are slow when opening files on Truecrypt volumes.

Another, less convenient method is to step in a debugger through the code in find-file and its subroutines, and see which part(s) there take such a long time.  Presumably, if this takes minutes, you should be able to identify the calls that take such a long time.

As a "leap of faith", how about timing the following, after starting "emacs -Q":

  M-: (insert-file-contents "SOME-FILE") RET

where SOME-FILE is a file on a Truecrypt volume.  Does the above take an abnormally long time, or is it as fast as when you do the same with a file on any other volume?

________________________________

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's Email System Administrator.






  reply	other threads:[~2023-12-12 17:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:43 bug#67672: EMACS - Slow opening files Chand, Suresh
2023-12-07  6:43 ` Eli Zaretskii
2023-12-07 16:39   ` Moore, Rider
2023-12-07 18:01     ` Eli Zaretskii
2023-12-07 18:16       ` Moore, Rider
2023-12-07 18:28         ` Eli Zaretskii
2023-12-08 21:41           ` Moore, Rider
2023-12-09  7:29             ` Eli Zaretskii
2023-12-11 17:16               ` Moore, Rider
2023-12-11 17:53                 ` Eli Zaretskii
2023-12-12 15:52                   ` Moore, Rider
2023-12-12 17:07                     ` Eli Zaretskii
2023-12-12 17:57                       ` Moore, Rider [this message]
2023-12-12 18:40                         ` Eli Zaretskii
2023-12-12 19:06                           ` Moore, Rider
2023-12-12 19:15                             ` Eli Zaretskii
2023-12-12 19:33                               ` Moore, Rider
2023-12-12 19:46                                 ` Eli Zaretskii
2023-12-12 19:58                                   ` Moore, Rider
2023-12-12 21:03                                     ` Ihor Radchenko
2023-12-12 21:18                                       ` Moore, Rider
2023-12-12 21:25                                         ` Ihor Radchenko
2023-12-12 21:25                                           ` Moore, Rider
2023-12-12 21:29                                             ` Moore, Rider
2023-12-12 21:43                                               ` Ihor Radchenko
2023-12-12 21:32                                             ` Ihor Radchenko
2023-12-12 21:38                                               ` Moore, Rider
2023-12-12 21:56                                                 ` Ihor Radchenko
2023-12-13 11:49                                                   ` Eli Zaretskii
2023-12-13 11:59                                                     ` Dmitry Gutov

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=CY8PR11MB71335EED101F6E673DD013A1AE8EA@CY8PR11MB7133.namprd11.prod.outlook.com \
    --to=rmoore@cooley.com \
    --cc=67672@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=schand@cooley.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).