From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: yyoncho <yyoncho@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Running process filters in another thread
Date: Sun, 30 Sep 2018 09:01:52 -0400 [thread overview]
Message-ID: <jwvh8i7jg6d.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CACCVLQV=NWm7RH5f2cABOtdmFQ+df199aXahbGrcoROAcS2Lgg@mail.gmail.com> (yyoncho@gmail.com's message of "Sun, 30 Sep 2018 10:08:06 +0300")
>> So, IIUC the scenario is that the LSP sends us large JSON data
>> structures, but we only ever use a fairly small portion of it, so
>> presumably a significant part of the total processing time is spent
>> gobbling data and parsing it into an internal data structure.
>
> AFAIK this is not the case, LSP is pretty minimal. This could be true
> for some limited cases but in general we need all of the data.
If we really use all of the data, then I can't see how processing the
bytes and parsing them can be the dominating factor, so
a `start-json-process` wouldn't make any significant difference.
But at least in your example of semantic highlight we definitely don't
have to use all of the data, but only the portion relevant for the
currently displayed parts of the buffer.
Stefan
next prev parent reply other threads:[~2018-09-30 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 18:21 Running process filters in another thread yyoncho
2018-09-28 21:14 ` Eli Zaretskii
[not found] ` <CACCVLQUrpxuhKwaHbFfCSzYLfucL8x+tJOkwgKwK8bzb0VZaWg@mail.gmail.com>
2018-09-29 6:54 ` Fwd: " yyoncho
2018-09-29 7:37 ` Eli Zaretskii
2018-09-28 23:03 ` Stefan Monnier
2018-09-29 7:35 ` yyoncho
2018-09-29 8:15 ` Eli Zaretskii
2018-09-29 18:10 ` Stefan Monnier
2018-09-29 19:23 ` yyoncho
2018-09-29 20:30 ` Stefan Monnier
2018-09-30 7:08 ` yyoncho
2018-09-30 13:01 ` Stefan Monnier [this message]
2018-09-30 15:01 ` yyoncho
2018-10-01 21:12 ` Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh8i7jg6d.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=yyoncho@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.