chore: clean up temporary files and reorganize documentation

- Delete temporary benchmark shell scripts (7 files)
- Delete temporary log files from root and integrationtests
- Delete .out test output files
- Delete temporary Python analysis scripts
- Move documentation to doc/ directory:
  - TURBOBOOST_OPTIMIZATION.md → doc/turboboost_optimization.md
  - performance_optimization_summary.md → doc/performance_optimization_summary.md
  - integrationtests/REFACTORING_GUIDE.md → doc/refactoring_guide.md
  - benchmarks/PROFILING.md → doc/profiling.md

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

1 files changed, 0 insertions, 62 deletions

diff --git a/performance_optimization_summary.md b/performance_optimization_summary.md
deleted file mode 100644
index 9d1162b..0000000
--- a/performance_optimization_summary.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# DTail Performance Optimization Summary
-
-## Changes Made
-
-### 1. Optimized Trace Logging (`/internal/io/dlog/dlog.go`)
-
-**Problem**: The `Trace()` and `Devel()` functions were calling `runtime.Caller(1)` for every invocation, even when trace logging was disabled. This was causing ~497ns overhead per call.
-
-**Solution**: Added early level checks before the expensive `runtime.Caller()` operation:
-
-```go
-func (d *DLog) Trace(args ...interface{}) string {
-    // Early check to avoid expensive runtime.Caller when trace is disabled
-    if d.maxLevel < Trace {
-        return ""
-    }
-    // ... rest of function
-}
-```
-
-### 2. Improved Buffering in Turbo Mode (`/internal/server/handlers/turbo_writer.go`)
-
-**Problem**: Turbo mode was forcing immediate flush after every line in serverless mode, defeating the purpose of buffering.
-
-**Solution**: Removed the immediate flush condition for serverless mode, allowing proper buffering:
-
-```go
-// Changed from:
-if w.writeBuf.Len() >= w.bufSize || w.serverless {
-    return w.flushBuffer()
-}
-
-// To:
-if w.writeBuf.Len() >= w.bufSize {
-    return w.flushBuffer()
-}
-```
-
-## Performance Results
-
-### Before Optimization
-- Turbo mode was **3-5x slower** than non-turbo mode
-- DCat (10MB): 678ms (turbo) vs 210ms (non-turbo)
-- DGrep (10MB): 570ms (turbo) vs 96ms (non-turbo)
-
-### After Optimization
-- Turbo mode is now **2.87x faster** than non-turbo mode
-- DCat (1M lines): 0.66s (turbo) vs 1.89s (non-turbo) - **65% improvement**
-- DCat with colors: 1.69s (turbo) vs 2.24s (non-turbo) - **24% improvement**
-
-## Verification
-- ✅ All unit tests pass
-- ✅ All integration tests pass
-- ✅ No functionality regression
-- ✅ Backward compatible
-
-## Files Modified
-1. `/internal/io/dlog/dlog.go` - Lines 196-216
-2. `/internal/server/handlers/turbo_writer.go` - Lines 104-108
-
-## Key Takeaway
-The trace logging overhead was the primary bottleneck, causing DTail to spend more time logging than processing data. By adding simple level checks before expensive operations, we achieved a ~3x performance improvement in turbo mode.
\ No newline at end of file