marcelroed/gigatoken

Language model tokenization at GB/s

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 16th, 2026
Created on November 10th, 2025
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 220
Total Stargazers: 4,106 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 hours
Mean response time: 2.9 days
90th percentile: 2.8 days
Tracked items: 19

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 46 days
Stale 30+ days: 14
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • hf-bug (3)
  • performance (2)
  • enhancement (1)
  • security (1)

Detailed Description

Gigatoken is a tokenizer that performs language model tokenization at gigabyte-per-second speeds. The tool addresses the performance bottleneck of tokenizing large text corpora for language model training and inference. It achieves this speed through a Rust implementation optimized for throughput, enabling rapid conversion of raw text into token sequences that models can process.

Developers working with large-scale language model pipelines should consider gigatoken when tokenization speed becomes a constraint in their workflow. The tool suits projects that need to process substantial volumes of text efficiently, such as training infrastructure, data preprocessing pipelines, or real-time inference systems where tokenization latency matters. It is particularly valuable for teams handling gigabyte-scale datasets where traditional tokenizers become a performance bottleneck.

The project shows consistent development activity with regular commits across multiple months. Work spans both core functionality improvements and maintenance tasks, indicating sustained attention to the codebase. The maintainer responds to issues and pull requests, demonstrating active engagement with users and contributors.