Can we improve merge performance?

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
data, performance

Research direction

No file or test is named. Start by locating the merger entry point and reproducing the slowdown with the finepdf English and nemotron-cc-1.0 medium datasets. Done means a measured improvement in merge performance without changing the resulting data.

Written by the indexing model from the issue text.

Description

idea

Merger are running on very big data in single thread. This is slow. Can we improve?

Some datasets with issues:
finepdf english
nemotron-cc-1.0 medium

Dominant language
Python
Stars
1
Forks
2
Avg merge
18h 22m
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenEuroLLM/training-data-packer

All issues in OpenEuroLLM/training-data-packer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.