Wanted: Review manager for std.data.json

Sönke Ludwig via Digitalmars-d digitalmars-d at puremagic.com
Thu Apr 9 01:59:56 PDT 2015


Am 08.04.2015 um 20:55 schrieb Iain Buclaw via Digitalmars-d:
> On 8 April 2015 at 20:32, tcha via Digitalmars-d
> <digitalmars-d at puremagic.com> wrote:
>> (...)
>> Also tried to dustmite the minimal failing version and here is a result:
>> http://pastebin.com/YjdvT3G4
>>
>> It's my first use of it so I hope it can help to solve this problem. It
>> outputs less errors, but also compiles fine in debug and fails to link in
>> release.

I've filed two tickets for linker errors (and added a workaround for the 
first one):
https://issues.dlang.org/show_bug.cgi?id=14425
https://issues.dlang.org/show_bug.cgi?id=14429

I'll try to reduce the pastebin reduced sample further, too, as it looks 
like it has yet another root cause.

>
> Frankly, if we are not as fast (or elegant) as Python's json library,
> it should be thrown out back to the drawing board.
>
> Iain.
>

As far as the profiler results can be trusted, a good chunk of the time 
gets spent for reading individual bytes from memory, but there must be 
something else low-level going on that make things this bad. However, 
there is nothing fundamental in the structure/design that would cause 
this, so I think spending more time with the profiler is the only 
logical step now. Unfortunately my VTune license has expired and perf on 
Linux makes the task quite a bit more involved.

If we want to be really fast, though, we need to add optimized SIMD 
paths, but this is currently outside of the possibilities of my time budget.


More information about the Digitalmars-d mailing list