JTigerNova.jtiger.util.io 1.0.3

JTiger.Util.IO

High-performance IO utilities for .NET applications.

FastFileLogger

A high-throughput, non-blocking file logger designed for production workloads.

Features

• Non-blocking writes: Log() and Error() enqueue messages instantly and return
• Background writer: Single dedicated task handles all file I/O
• Automatic rotation: Rotates log files when size exceeds threshold (default 1MB)
• Retry with backoff: Handles transient file locks gracefully
• Graceful shutdown: Flushes remaining messages on dispose
• Thread-safe: Safe to call from multiple threads concurrently

Quick Start

using jtiger.util.io;

// Create logger
using var logger = new FastFileLogger("logs/app.log");

// Log messages (non-blocking)
logger.Log("Application started");
logger.Error("Something went wrong", exception);

Configuration

var logger = new FastFileLogger(
 path: "logs/app.log",
 maxBytes: 10 * 1024 * 1024, // Rotate at 10MB (default: 1MB)
 maxBatchLines: 256, // Max lines per batch (default: 256)
 maxBatchBytes: 64 * 1024, // Max bytes per batch (default: 64KB)
 maxWriteRetries: 6, // Retry attempts on failure (default: 6)
 baseRetryDelayMs: 10, // Base retry delay (default: 10ms)
 maxRequeueAttempts: 3, // Max requeue on failure (default: 3)
 maxMessageLength: 16 * 1024, // Max message length (default: 16KB)
 onWriteError: ex => Console.Error.WriteLine($"Log write failed: {ex.Message}")
);

Log Format

Tab-delimited format for easy parsing:

2024-01-15T10:30:00.0000000+00:00	INFO	T12	Application started
2024-01-15T10:30:01.0000000+00:00	ERROR	T12	Database connection failed	EX:System.Exception: Connection timeout...

File Rotation

When the log file exceeds maxBytes:

1. Attempts to rename current file to {filename}.old
2. Falls back to truncation if rename fails (file locked)
3. Continues appending if both fail (retries on next write)

Thread Safety

All public methods are thread-safe. Multiple threads can call Log() and Error() concurrently without synchronization.

Disposal

Always dispose the logger to ensure remaining messages are flushed:

// Using statement (recommended)
using var logger = new FastFileLogger("app.log");

// Or explicit dispose
logger.Dispose();

The logger waits up to 5 seconds during disposal to flush queued messages.