You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The serialization code generated by asn1scc during OG3 was unexpectedly slow. Just to make sure something was not wrong in our setup we benchmarked it versus other serializers:
No, the supported encodings are uPER and ACN.
Is your concern encoding time or compactness? They may be contradictory.
Note that in a TASTE interface you can select "native" encoding so that the data is transferred in native representation, without encoding delay. The requisite is that the two functions are deployed on systems with the same binary representation (mainly endianness).
The serialization code generated by asn1scc during OG3 was unexpectedly slow. Just to make sure something was not wrong in our setup we benchmarked it versus other serializers:
The code is available here:
https://gitlab.com/h2020src/og7/cpp-serializers
This test did not include large datasets.
Struct {
int64[1000]
char[100][86]
}
Can OER encoding be triggered somehow instead of uPER (which is not as compact as it should be (specially compared to other solutions) )?
The text was updated successfully, but these errors were encountered: