cloudpipe / cloudpipe/cloudpickle

Why is the first deserialization slow in the container?

Open
#421 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.9k
Forks
195
Avg merge
1d 10h
Merged PRs (30d)
1

Description

The serialized function is complex, which introduce some dependencies, but the number of lines of code for the overall function is not long.
![image](https://user-images.githubusercontent.com/29364768/117746219-9d32ca00-b23e-11eb-8d69-653ea7e7be77.png)
Running outside the container is as fast as a non-first run inside the container, What should I do to speed up the first deserialization in a container?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no source file or test. Start by reproducing the first-versus-subsequent deserialization timings inside and outside the container, then trace the serialized function and its dependencies to isolate the first-run cost. Done means the first deserialization in the container is measurably faster, with the comparison documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.