From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: yyoncho Newsgroups: gmane.emacs.bugs Subject: bug#31138: Native json slower than json.el Date: Sun, 21 Apr 2019 14:38:04 +0300 Message-ID: References: <87sh806xwa.fsf@chapu.is> <83r2awnw0w.fsf@gnu.org> <83d0mgnn31.fsf@gnu.org> <835zs7och6.fsf@gnu.org> <83tvfqnbxc.fsf@gnu.org> <83lg12n75s.fsf@gnu.org> <83h8bqn2ik.fsf@gnu.org> <83zhphliil.fsf@gnu.org> <181b93a3-3861-0481-1b95-8344410d1049@yandex.ru> <83r2a2hdxn.fsf@gnu.org> <21f68973-a684-2a65-82eb-c8f3df90127f@yandex.ru> <83d0lmgez2.fsf@gnu.org> <7d503be9-4d85-3d0b-6829-631ad376ba3d@yandex.ru> <831s22gcci.fsf@gnu.org> <83y349gasn.fsf@gnu.org> <83d0lfag4x.fsf@gnu.org> <5cf45a21-65c3-67ee-f123-be83a6ee7c99@yandex.ru> <83a7gjaen6.fsf@gnu.org> <837ebnabkf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000adbc96058708c9f4" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="25609"; mail-complaints-to="usenet@blaine.gmane.org" Cc: =?UTF-8?Q?S=C3=A9bastien?= Chapuis , Dmitry Gutov , 31138@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Apr 21 13:44:56 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hIAty-0006TG-Mu for geb-bug-gnu-emacs@m.gmane.org; Sun, 21 Apr 2019 13:44:54 +0200 Original-Received: from localhost ([127.0.0.1]:51956 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hIAtx-0007lu-Mn for geb-bug-gnu-emacs@m.gmane.org; Sun, 21 Apr 2019 07:44:53 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42921) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hIAto-0007hz-VF for bug-gnu-emacs@gnu.org; Sun, 21 Apr 2019 07:44:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hIAoI-0006UO-7Y for bug-gnu-emacs@gnu.org; Sun, 21 Apr 2019 07:39:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34347) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hIAoI-0006U3-4h for bug-gnu-emacs@gnu.org; Sun, 21 Apr 2019 07:39:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hIAoH-0007lF-UM for bug-gnu-emacs@gnu.org; Sun, 21 Apr 2019 07:39:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: yyoncho Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 21 Apr 2019 11:39:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31138 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 31138-submit@debbugs.gnu.org id=B31138.155584670529789 (code B ref 31138); Sun, 21 Apr 2019 11:39:01 +0000 Original-Received: (at 31138) by debbugs.gnu.org; 21 Apr 2019 11:38:25 +0000 Original-Received: from localhost ([127.0.0.1]:47891 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hIAng-0007kP-Vj for submit@debbugs.gnu.org; Sun, 21 Apr 2019 07:38:25 -0400 Original-Received: from mail-lf1-f53.google.com ([209.85.167.53]:45376) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hIAne-0007kC-NA for 31138@debbugs.gnu.org; Sun, 21 Apr 2019 07:38:23 -0400 Original-Received: by mail-lf1-f53.google.com with SMTP id t11so7068507lfl.12 for <31138@debbugs.gnu.org>; Sun, 21 Apr 2019 04:38:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ghFIa9OYP4LMUuE/3gwTuFVoTD8g6/CFtAeS5vp5fFA=; b=AwJba8IGkcau4qFJ1SYm1c4CzWbkO1+iY9SgRDHihKwcYo/5DvtMaxOrJpYaiyuZj6 YknkJZHmhECb3SY6CRG99gXsBgyhftkVzYR/kQCIKqqXY3DcqXj41t/COaOgWnOGzHlB xYm5OivkIB3/bMYXOWSGB0fWrnmwTV8q4l4PHvEGOkCAjtFR6rw4UQVcSqnIc8hVVc43 FZRbMQFXxbahmpNot5Zb3CrZKrrP4iq/txIw1quc74dfv2pcR8G88sO46mEoiTL8KWIi MlZWvesCFtbGDCNN7oPg5XNC5k8+36z4F0wJkwHD+95nzCvDzDhXSrGnkU37K46jPC6p UbhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ghFIa9OYP4LMUuE/3gwTuFVoTD8g6/CFtAeS5vp5fFA=; b=mrpKNCzD2J425OgMoToTA97Dfdz+zLPNP+6s01HekLP/XshN7PTgwuc3I+hGVrfMb6 LDzlhs3/bN1l5+77ijKybk+FAAgd1FkCnqgKNdQHjcJrGBgKk0Nh/WVRB4K4TgD8ttri WbLi8Qanp1yb7qYyVgkpNiV//jXWOJFh5dTHg2nidOUL56AXyTeMorKVESmVbBxgPuol HKmjktLlyWo5+/P/0z3OBf3xt0Z4U9lOVzPnssA+qH6gp1ZrkwKZstc2Gu53by/7LDUE 7bYgFc160xk+4wcNC+GrdfsP7qGfmPtSywYvKblnVJX2nSr3IovsqXhHPLIaBNbeGt1c +cFg== X-Gm-Message-State: APjAAAU+7wfydfePCEbC8B7WNYRwNVbWuDjk58k1rR7bjMz7rpJs2iQ7 HljvwcAtJogyZWSq1Hxw6wgZexYbBNe2e16xXLQ= X-Google-Smtp-Source: APXvYqxXf/cGIolhvc4hcjYLW08y6sNbA2l7R/74P7NibW7QeHw5fm8ooUD/ApbloBZz1CLvJpZJWr6zvkqX1z0zR2E= X-Received: by 2002:ac2:5a11:: with SMTP id q17mr7449113lfn.145.1555846696646; Sun, 21 Apr 2019 04:38:16 -0700 (PDT) In-Reply-To: <837ebnabkf.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:157938 Archived-At: --000000000000adbc96058708c9f4 Content-Type: text/plain; charset="UTF-8" Hi Eli, I don't see how this follows, when this discussion clearly established > that native JSON parsing is much faster than parsing in Lisp. > We also established that current native performance is not fast enough to handle real-world scenarios. > I also don't see where did "a lot of time" come from, I think it's an > exaggeration, given the processing speed shown by benchmarks in this > discussion. > I said that *if* this is the case. You said that if 50% is spent in decoding it is not enough to justify the risk of crashing emacs. What I am saying is that IMO if 50% of the time is spent in decoding data that comes from Jansson it will be enough to justify not using Jansson at all and writing the whole Json parsing in Emacs Source tree. Thanks, Ivan --000000000000adbc96058708c9f4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Eli,

I don't see how thi= s follows, when this discussion clearly established
that native JSON parsing is much faster than parsing in Lisp.

We also established that current native performance = is not fast enough to handle real-world scenarios.=C2=A0
=C2=A0
I also don't see where did "a lot of time" come from, I think= it's an
exaggeration, given the processing speed shown by benchmarks in this
discussion.

I said that *if* this is th= e case. You said that if 50% is spent in decoding it is not enough to justi= fy the risk of crashing emacs. What I am saying is that IMO if 50% of the t= ime is spent in decoding data that comes from Jansson it will be enough to = justify not using Jansson at all and writing the whole Json parsing in Emac= s Source tree.

Thanks,
Ivan=C2=A0
<= /div>
--000000000000adbc96058708c9f4--