Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider native serializer support for numpy.ndarray #231

Open
1 task done
gsmecher opened this issue Apr 15, 2024 · 3 comments
Open
1 task done

Consider native serializer support for numpy.ndarray #231

gsmecher opened this issue Apr 15, 2024 · 3 comments

Comments

@gsmecher
Copy link

Things to check first

  • I have searched the existing issues and didn't find my feature already requested there

Feature description

Currently, the easiest way to serialize numpy.ndarrays using cbor2 is something like (neglecting error checks)

import numpy as np
import cbor2

x = np.ones(10)
y = cbor2.dumps(x, default=lambda x, y: x.encode(y.tolist()))

This requires numpy to traverse the array and convert it to a Python list, which is then handed off to cbor2 for another traversal - there are several traversals and transient allocations involved.

Because both Numpy and CBOR have clean C APIs, would you consider a direct conversion implemented in the C extension module? It's worth noting that the orjson JSON library does this already.

Use case

Low-overhead serialization of numpy arrays.

@agronholm
Copy link
Owner

I'm open to the idea if this can be done cleanly. What should ndarrays serialize to, in CBOR terms?

@gsmecher
Copy link
Author

Oops, I see this is already discussed in #59.

It looks like there are some options:

  1. Homogeneous typed arrays per RFC 8746
  2. Classic CBOR arrays with individual type tags
  3. Some numpy-specific type tag

The combination of (1) and (2) seems ideal, with (1) as a fastpath and (2) as a fallback. I'm optimistic Python ndarrays carry enough type metadata to decide between them without traversing the array.

(3) seems easy to rule out, and I'm only including it to say so out loud.

@agronholm
Copy link
Owner

Option 1 sounds like the best for encoding, but decoding may be an issue, particularly when numpy isn't present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants