From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Performance degradation from long lines Date: Fri, 26 Oct 2018 11:18:55 -0400 Message-ID: References: <665d5f3d84c071632f87f66ffedb6aed@webmail.orcon.net.nz> <589d82cf2910c03e7e7e008816f3b614@webmail.orcon.net.nz> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1540567101 24192 195.159.176.226 (26 Oct 2018 15:18:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 26 Oct 2018 15:18:21 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 26 17:18:16 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gG3sO-0006C7-PA for ged-emacs-devel@m.gmane.org; Fri, 26 Oct 2018 17:18:16 +0200 Original-Received: from localhost ([::1]:60648 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gG3uV-0008AE-2Z for ged-emacs-devel@m.gmane.org; Fri, 26 Oct 2018 11:20:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43308) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gG3ta-00084G-EH for emacs-devel@gnu.org; Fri, 26 Oct 2018 11:19:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gG3tI-0002vz-2x for emacs-devel@gnu.org; Fri, 26 Oct 2018 11:19:22 -0400 Original-Received: from [195.159.176.226] (port=56113 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gG3tH-0002vB-QV for emacs-devel@gnu.org; Fri, 26 Oct 2018 11:19:11 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1gG3r2-0004SN-JI for emacs-devel@gnu.org; Fri, 26 Oct 2018 17:16:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 22 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:TTsjBFNRZeXWYAHuwOAh3jQELWg= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:230709 Archived-At: >> Then I tried opening the 663K minified JSON file with 671209 >> characters on one line. > Just for comparison, the test file I've mostly been using is > the one from https://emacs.stackexchange.com/q/598 which is a > 18M single-line JSON file with 18922366 characters on one line, > which opens in about a second on my machine when so-long has > been enabled. I think Mithraeum's point is a good one: it would be worthwhile also to see what it is that the user wants to do with those kinds of files, because the slowness is but one of the problems. E.g. if you take your above example, maybe it does take just a second to open in so-long-mode, but what happens when you do M-> ? Is the "show the first screen" use case the main one (after which the user will see that the file format is not the right one, will change it (e.g. by pretty-printing it), and try again), or do we also want to care about what happens if the user then goes on to navigate in this buffer? Stefan