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

Serialization and deserialization too slow #23

Closed
trbKnl opened this issue Oct 29, 2024 · 1 comment · Fixed by #26
Closed

Serialization and deserialization too slow #23

trbKnl opened this issue Oct 29, 2024 · 1 comment · Fixed by #26
Assignees
Labels
bug Something isn't working

Comments

@trbKnl
Copy link
Collaborator

trbKnl commented Oct 29, 2024

Serialization and deserialization of objects to pass between pydodide and the main threat causes very large donation to fail with memory overflows.

@trbKnl trbKnl self-assigned this Oct 29, 2024
@trbKnl trbKnl added the bug Something isn't working label Oct 29, 2024
@trbKnl
Copy link
Collaborator Author

trbKnl commented Oct 30, 2024

Serialization is not necessary. Make it optional.

This means to pd.DataFrame.to_json() step is skipped. But also json.dumps can be avoided. Both options consume too much memory.

This means data needs to be extracted into the dict equivalent of pd.DataFrame.to_json().

solution

send back dict object like so:

{ 
    "variable_x": {"0":1},
    "variable_x": {"0":1},
}

This results in tables being able to load massive amounts of data:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant