Re: Slow completion-at-point

["T.V Raman" <raman@google.com>]

Dmitry Gutov <dmitry@gutov.dev> writes:


Not sure if you saw my message where I tracked down the culprit:
The slowness in completion-at-point is triggered if
Completion Auto Help: Choice: Value Menu Always visible.

is set as above, it gets janky; if you go back to the default it
performs normally.

> On 09/11/2023 09:22, Juri Linkov wrote:
>>> Here is some timing information for this issue:
>>>
>>> I added the following around advice fragment to completion-at-point debug:
>>>
>>> (let ((start (current-time)))
>>>       ad-do-it
>>>       (message "<%.4f %d gcs %.4f>"
>>>                (float-time (time-subtract (current-time) start))
>>>                gcs-done gc-elapsed))
>>>
>>> Then I went to a shell buffer, and from my home directory (it contains
>>> a subdir text) typed
>>>
>>> cd te <tab>
>>>
>>> Messages buffer shows the following:
>>>
>>> ~/
>>> Making completion list...
>>> Sole completion
>>> <2.0219 14 gcs 1.2927>
>> Please try to get benchmark numbers after customizing the recently added
>> 'completion-lazy-hilit'.
>
> completion-lazy-hilit is not a user option. It's a defvar, intended
> for completion frontends to opt into deferred highlighting performed
> by completions styles.
>
> IOW, whenever each completion UI is updated (that uses completion
> styles -- that is, calls completion-all-completions), all its users
> will see the benefits.
>

--