kopper :colon_three: @kopper@not-brain.d.on-t.work
Public
@hongminhee洪 民憙 (Hong Minhee) :nonbinary: take this part with a grain of salt because my benchmarks for it are with dotNetRdf which is the slowest C# implementation i know of (hence my replacement library), but JSON-LD is slower than RSA validation, which is one of the pain points around authorized fetch scalability

wetdry.world/@kopper/114678924693500011

no longer kopper (@kopper@wetdry.world)

``` | Method | Mean | Error | StdDev | Gen0 | Allocated | |------------------ |---------:|---------:|---------:|-------:|----------:| | RsaValidation | 19.77 μs | 0.043 μs | 0.033 μs | 0.1526 | 3.16 KB | | FlattenYesContext | 7.907 ms | 0.0788 ms | 0.0658 ms | 171.8750 | 46.8750 | 4.01 MB | | Frame | 12.342 ms | 0.0810 ms | 0.0677 ms | 250.0000 | 78.1250 | 5.94 MB | ```

wetdry.world · Wet-Dry World

kopper :colon_three: @kopper@not-brain.d.on-t.work
Public
@hongminhee洪 民憙 (Hong Minhee) :nonbinary: if i can give one piece of advice to devs who want to process JSON-LD: dont bother compacting. you already know the schema you output (or you're just passing through what the user gives and it doesn't matter to you), serialize directly to the compacted representation, and only run expansion on incoming data

expansion is the cheapest JSON-LD operation (since all other operations depend on it and run it internally anyhow), and this will get you all the compatibility benefits of JSON-LD with little downsides (beyond more annoying deserialization code, as you have to map the expanded representation to your internal structure which will likely be modeled after the compacted one)
0
1
0

If you have a fediverse account, you can quote this note from your own instance. Search https://not-brain.d.on-t.work/notes/aihdln35y3z7y1hw on your instance and quote it. (Note that quoting is not supported in Mastodon.)