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

Large Task Deserialization Time during Optimization #333

Closed
Jiaweihu08 opened this issue Jun 13, 2024 · 0 comments · Fixed by #334
Closed

Large Task Deserialization Time during Optimization #333

Jiaweihu08 opened this issue Jun 13, 2024 · 0 comments · Fixed by #334
Assignees
Labels
type: bug Something isn't working

Comments

@Jiaweihu08
Copy link
Member

What went wrong?

There's an enormous task deserialization time during optimizations—specifically the last collect from RollupDataWriter.compact().

The IndexStatus.cubeStatuses is packaged within each task, and their size increases as the metadata size increases.

How to reproduce?

Try to optimize a relatively large table and compare the Task Deserialization Time from the second collect with that from the execute.; The values from execute should be an order of magnitude smaller.

2. Branch and commit id: main, b7f1906

3. Spark version: 3.5.0

4. Hadoop version: 3.3.4

5. How are you running Spark? locally, distributed

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

Successfully merging a pull request may close this issue.

1 participant