Chunk-Based Navigation

Grep Badger streams logs in chunks instead of loading the full file into memory at once.

This helps keep memory usage low and makes large files quicker and easier to work with.

For this reason, line numbers are estimated. This includes the Go to line functionality.

1. What chunking means

A chunk is a section of the log file that Grep Badger loads into the viewer.

Instead of opening the entire file at once, Grep Badger loads only the part you need right now.

This is especially useful for very large local and remote log files.

2. Open a log file

1. Click the + icon to the right of Files in the left sidebar.
2. In the file explorer, select your host.
3. Navigate to the log file you want to open.

Once you select a log file, Grep Badger opens it in the main view and begins tailing the file with a clear history.

3. Use chunk controls

Chunk navigation is done in the CONTROLS section in the left sidebar.

You can:

• Load Latest to jump to the newest chunk
• Previous to move backward
• Next to move forward
• Go to a line to jump near a specific part of the file

These controls help you move through large files without loading everything at once.

4. Go to a line

Use Go when you want to jump near a specific line number.

This is useful when:

• you need to quickly navigate to a section of the file
• you want to return to a part of the file quickly
• you are comparing one section of the file to another

Due to streaming, line numbers are estimated. When navigating to a line, treat it as a ballpark rather than a definitive position.

5. Chunking and tailing

When you use chunk navigation, tailing will be paused.

This lets you inspect older or nearby parts of the file without the view changing while new lines arrive.

When you start tailing again, the latest chunk will always be loaded first.

6. Why Grep Badger uses chunking

Chunking helps Grep Badger:

• handle very large files
• stay responsive
• avoid loading the full file into memory
• work better across slower remote connections

This applies to both local files and remote files streamed over SSH/SFTP.

7. Chunk size

The default chunk size is 1000.

This can be changed in settings.

A larger chunk size may show more data at once, but it can also increase memory usage and affect performance.

Important notes

• Very large files may take a moment to load depending on file size and network speed.
• Remote log files are streamed through SSH/SFTP. They may be slower than local files.
• If you want to return to live output, use Load Latest or start tailing again.