DEV Community

y4u profile picture

y4u

Building UwView — a viewer for huge logs & text files, tested with a 258 GB / 4.5-billion-line real-world file. 40 years in CAD/GIS. Windows95-era tool, rebuilt in C#/Avalonia.

Location oita,japan Joined Joined on  Personal website https://uvp.y42u.net/en/pro-en/ github website

Education

Electronics / radio engineering

Work

Independent developer (40+ yrs). Building UwView & geospatial/surveying apps.

How to Open a 50GB Log File — and Reopen It in 0.05 Seconds. A klogg Alternative, Benchmarked

How to Open a 50GB Log File — and Reopen It in 0.05 Seconds. A klogg Alternative, Benchmarked

Comments
6 min read
[In Development] Editing a 48GB File and Saving Mid-Way: EmEditor vs UwEditor Pro

[In Development] Editing a 48GB File and Saving Mid-Way: EmEditor vs UwEditor Pro

Comments
8 min read
[In Development] I Replaced 21,994 Occurrences in a 10GB, 100-Million-Line File in 16.8 Seconds

[In Development] I Replaced 21,994 Occurrences in a 10GB, 100-Million-Line File in 16.8 Seconds

Comments
5 min read
Find Only Where 'New York Central Park coffee_shop' Appear in That Order — Sequence Search on a 258 GB Local File

Find Only Where 'New York Central Park coffee_shop' Appear in That Order — Sequence Search on a 258 GB Local File

Comments
3 min read
From 100,492 Hits to 3 in Two Clicks — Drill-down Search for Huge Local Files

From 100,492 Hits to 3 in Two Clicks — Drill-down Search for Huge Local Files

Comments
3 min read
I Benchmarked My Free Viewer Against EmEditor and klogg — Honestly

I Benchmarked My Free Viewer Against EmEditor and klogg — Honestly

Comments
2 min read
You Found the ERROR. The Cause Is in the Lines Before It

You Found the ERROR. The Cause Is in the Lines Before It

Comments
3 min read
"File Too Large to Open" — Investigating a 50 GB Log Without Splitting It

"File Too Large to Open" — Investigating a 50 GB Log Without Splitting It

Comments
2 min read
My Fanless Mac Skewed My Benchmark by 54% — Thermal Throttling and Round-Robin Measurement

My Fanless Mac Skewed My Benchmark by 54% — Thermal Throttling and Round-Robin Measurement

Comments
3 min read
How Many Search Threads Is the Right Number? I Measured 0.89 Billion Lines at 1-16 Threads

How Many Search Threads Is the Right Number? I Measured 0.89 Billion Lines at 1-16 Threads

Comments
3 min read
Reading Huge Logs by Color — a Highlighter That Doesn't Stutter at 100 Million Lines

Reading Huge Logs by Color — a Highlighter That Doesn't Stutter at 100 Million Lines

Comments
4 min read
I Rebuilt My 30-Year-Old Text Viewer in C#/Avalonia — It Matched the Industry-Standard klogg. Then I Redesigned It for Today's Hardware.

I Rebuilt My 30-Year-Old Text Viewer in C#/Avalonia — It Matched the Industry-Standard klogg. Then I Redesigned It for Today's Hardware.

Comments
6 min read
Shelve an Investigated Log at 1/9th the Size, Reopen It Tomorrow Right Where You Left Off

Shelve an Investigated Log at 1/9th the Size, Reopen It Tomorrow Right Where You Left Off

Comments
4 min read
I Expanded the Entire US OpenStreetMap to a Single 258 GB XML File — 4,509,830,821 Lines, and What Broke

I Expanded the Entire US OpenStreetMap to a Single 258 GB XML File — 4,509,830,821 Lines, and What Broke

Comments
5 min read
Why We Split Search Results Into a Separate Window — Jump, Save, and Context Lines You Can Use \"While Looking\" With the Filter Popup

Why We Split Search Results Into a Separate Window — Jump, Save, and Context Lines You Can Use \"While Looking\" With the Filter Popup

Comments
4 min read
How much slower is the browser build, really? — UwView native (UVF) vs WASM, measured on the same file

How much slower is the browser build, really? — UwView native (UVF) vs WASM, measured on the same file

Comments
3 min read
I Opened 51GB / 890M Lines of Real Data — Then Calculated How Far It Could Theoretically Go (~9.2 Quintillion Lines)

I Opened 51GB / 890M Lines of Real Data — Then Calculated How Far It Could Theoretically Go (~9.2 Quintillion Lines)

Comments
8 min read
An honest comparison with klogg [v1.1.1]: I list every row I'm losing on, too

An honest comparison with klogg [v1.1.1]: I list every row I'm losing on, too

Comments
5 min read
I benchmarked my log viewer against klogg at 3/10/48 GB — the second open is the real win

I benchmarked my log viewer against klogg at 3/10/48 GB — the second open is the real win

Comments
4 min read
loading...