Re: On elisp running native

[Andrea Corallo]

Eli Zaretskii <address@hidden> writes:

>> From: yyoncho <address@hidden>
>> Date: Tue, 25 Feb 2020 08:14:02 +0200
>> Cc: Eli Zaretskii <address@hidden>, Stefan Monnier <address@hidden>,
>>  emacs-devel <address@hidden>
>> 
>> I did benchmarks of json parsing here it is what I get:
>> 
>>   | test         | non-gc avg (s) | gc avg (s) | gcs avg | tot avg (s) | tot 
>> avg err (s) |
>>   
>> |--------------+----------------+------------+---------+-------------+-----------------|
>>   | json-parsing |           2.57 |       3.32 |     318 |        5.89 |     
>>        0.10 |
>>   
>> |--------------+----------------+------------+---------+-------------+-----------------|
>>   | total        |           2.57 |       3.32 |     318 |        5.89 |     
>>        0.10 |
>> 
>> Native:
>> 
>>   | test         | non-gc avg (s) | gc avg (s) | gcs avg | tot avg (s) | tot 
>> avg err (s) |
>>   
>> |--------------+----------------+------------+---------+-------------+-----------------|
>>   | json-parsing |           1.71 |       4.31 |     343 |        6.02 |     
>>        0.01 |
>>   
>> |--------------+----------------+------------+---------+-------------+-----------------|
>>   | total        |           1.71 |       4.31 |     343 |        6.02 |     
>>        0.01 |
>> 
>> It looks like this is bellow the average speedup you might wanna take a look:
>
> I think this might be expected, since most of the heavy processing in
> this benchmark is in C, and thus not affected by the compiling Lisp
> into native machine code.

Yeah, the interesting part would be the GC one.  I'm wondering if that's
just a noise artifact or not.

Andrea

-- 
address@hidden