The metadata serialization format affects the API performance.
This is less pronounced in the latest arche-core versions but still noticeable.
If you just want to know the best solutions:
application/n-triples
. It’s definitely the fastest to
serialize on the ARCHE side and most probably the fastest to parse on
your application side (with the only exception of JS where
application/ld+json
is probably the fastest to parse).text/turtle
.A few tests were performed on a copy of the ARCHE production instance containing 336k resources and 11.8M triples.
text/turtle
is the
most time consuming (roughly 50% more than other formats) and
application/n-triples
is the fastest serialization
format.application/ld+json
which is
the slowest for small triples count (with the current ARCHE production
instance settings below 1000 triples). This is because in such a case
the result is reshaped to have a more compact structure while for larger
triples count just a streaming JSON-LD serializer is used.