Batch File Processing Implementation on Server

We regularly encounter situations where a client needs to import 50,000 rows from CSV. Our batch file processing implementation leverages Laravel queue jobs for parallel data processing, ensuring stable import of large files without memory leaks. Without a clear batch processing strategy, such tasks lead to OOM and endless timeouts. Our experience shows: proper architecture cuts processing time by 10x and prevents data loss. It doesn't matter if you work with dozens or hundreds of thousands of records — the patterns remain the same.

Key Problems in Batch Processing

Memory. Loading the entire CSV into an array is a sure way to exhaust memory. The correct pattern is streaming reads in chunks. We use Laravel's LazyCollection, which reads the file line by line without loading into memory. This approach also optimizes database connection pooling and queue throughput.

Partial errors. If out of 10,000 rows 50 are invalid — stopping the entire process is wrong. Our logic: skip problematic rows, log with context (e.g., the erroneous record's email), and continue.

Resumability. If the process fails on row 7,000 — we don't start over. Laravel Batch allows resuming from the point of failure, preserving already processed chunks. Batch atomicity is maintained through state tracking in job_batches table.

Parallelism. Sequential processing of 50,000 records at 100ms each takes almost 1.5 hours. Splitting into parallel jobs (optimal chunk size 500 records) reduces this to 5–10 minutes on 4 workers. Worker concurrency is configured for optimal load using queue worker process management (Supervisor with numprocs=4).

How to Avoid Memory Leaks When Importing Large CSV?

We apply the "Batch → Chunks → Jobs" pattern. After file upload, a master task splits data into chunks; each chunk is processed by a separate job in parallel. After all jobs complete, an aggregation task runs.

namespace App\Services;

use Illuminate\Bus\Batch;
use Illuminate\Support\Facades\Bus;
use Illuminate\Support\LazyCollection;

class CsvImportService
{
    private const CHUNK_SIZE = 500;

    public function startImport(string $filePath, int $importId): string
    {
        $jobs = [];

        LazyCollection::make(function () use ($filePath) {
            $handle = fopen($filePath, 'r');
            $header = fgetcsv($handle);
            while (($row = fgetcsv($handle)) !== false) {
                yield array_combine($header, $row);
            }
            fclose($handle);
        })
        ->chunk(self::CHUNK_SIZE)
        ->each(function ($chunk, $index) use (&$jobs, $importId) {
            $jobs[] = new ProcessCsvChunkJob(
                importId: $importId,
                chunkIndex: $index,
                rows: $chunk->values()->toArray()
            );
        });

        $batch = Bus::batch($jobs)
            ->name("csv-import-{$importId}")
            ->allowFailures()
            ->then(function (Batch $batch) use ($importId) {
                Import::find($importId)?->update(['status' => 'completed']);
                ImportCompletedEvent::dispatch($importId);
            })
            ->catch(function (Batch $batch, \Throwable $e) use ($importId) {
                Import::find($importId)?->update([
                    'status' => 'partially_failed',
                    'error_message' => $e->getMessage(),
                ]);
            })
            ->finally(function (Batch $batch) use ($importId) {
                $import = Import::find($importId);
                $import?->update([
                    'total_jobs' => $batch->totalJobs,
                    'failed_jobs' => $batch->failedJobs,
                    'finished_at' => now(),
                ]);
            })
            ->onQueue('batch-processing')
            ->dispatch();

        Import::find($importId)?->update(['batch_id' => $batch->id]);
        return $batch->id;
    }
}

Chunk Processing Job

class ProcessCsvChunkJob implements ShouldQueue
{
    use Batchable, Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    public int $tries = 3;
    public int $timeout = 120;
    public int $backoff = 10;

    public function __construct(
        private int $importId,
        private int $chunkIndex,
        private array $rows
    ) {}

    public function handle(): void
    {
        if ($this->batch()?->cancelled()) {
            return;
        }

        $successCount = 0;
        $errors = [];

        foreach ($this->rows as $lineNum => $row) {
            try {
                $this->processRow($row);
                $successCount++;
            } catch (\Throwable $e) {
                $errors[] = [
                    'chunk' => $this->chunkIndex,
                    'line' => $lineNum,
                    'data' => array_slice($row, 0, 3),
                    'error' => $e->getMessage(),
                ];
            }
        }

        ImportChunkResult::create([
            'import_id' => $this->importId,
            'chunk_index' => $this->chunkIndex,
            'processed' => count($this->rows),
            'succeeded' => $successCount,
            'failed' => count($errors),
            'errors' => $errors,
        ]);

        Import::where('id', $this->importId)->increment('processed_rows', count($this->rows));
        Import::where('id', $this->importId)->increment('success_rows', $successCount);
    }

    private function processRow(array $row): void
    {
        $validated = validator($row, [
            'email' => 'required|email',
            'name' => 'required|string|max:255',
        ])->validate();

        User::updateOrCreate(
            ['email' => $validated['email']],
            ['name' => $validated['name']]
        );
    }
}

What If the Process Interrupts?

Laravel Batch saves state in the job_batches table. Completed chunks are marked as done; incomplete ones automatically resume on worker restart. For forced restart, you can query unfinished chunk indices from ImportChunkResult and re-dispatch jobs.

Real-time progress is exposed via an endpoint:

public function progress(int $importId): JsonResponse
{
    $import = Import::findOrFail($importId);
    $batch = $import->batch_id ? Bus::findBatch($import->batch_id) : null;

    return response()->json([
        'status' => $import->status,
        'processed_rows' => $import->processed_rows,
        'success_rows' => $import->success_rows,
        'total_rows' => $import->total_rows,
        'percentage' => $import->total_rows > 0
            ? round($import->processed_rows / $import->total_rows * 100, 1)
            : 0,
        'batch' => $batch ? [
            'total_jobs' => $batch->totalJobs,
            'pending_jobs' => $batch->pendingJobs,
            'failed_jobs' => $batch->failedJobs,
            'progress' => $batch->progress(),
        ] : null,
    ]);
}

Load Throttling

For the batch queue, a dedicated worker pool with limited parallelism prevents overwhelming the DB or CPU:

[program:batch-worker]
command=php artisan queue:work --queue=batch-processing --max-jobs=50 --sleep=3 --timeout=120
numprocs=4
autostart=true
autorestart=true

numprocs=4 — four workers, each processing chunks sequentially. --max-jobs=50 — after 50 jobs, the worker restarts to free memory.

We choose 500 as the optimal balance between speed and stability. Our batch implementation processes 50,000 records 10x faster than sequential processing.

Work Process

1. Analysis: Study file format, data volume, speed requirements.
2. Design: Select chunk size, configure queues.
3. Implementation: Write code with chunks, error handling, progress, and resumability.
4. Testing: Run on test data with simulated failures.
5. Deploy: Configure workers, monitoring, hand over documentation.

What's Included in Turnkey Implementation

• Batch processing architecture with chunks and parallel jobs.
• Progress and recovery endpoint.
• Detailed error logging for analysis.
• Deployment and operational documentation.
• Team training on system usage.
• One month post-launch support.

Timeline and Cost

Basic CSV import implementation with chunks and progress — from 1 business day. Adding resumability, detailed logs, and XLSX/JSON support — another 1–2 days. For a standard CSV import with chunks and progress, the turnkey cost is $1,500. The typical cost savings for a mid-sized business exceed $20,000 annually due to reduced manual processing. With 5+ years on the market and over 50 batch-processing projects completed, we guarantee stability and scalability.

Advantages of Bus::batch()

Laravel Bus::batch() documentation provides built-in support for grouped tasks: status tracking, partial failures, callback chains. This eliminates writing your own scheduler and reduces error risk.

Server-Side CSV Import and Large File Processing in PHP

Our expertise includes server-side CSV import, parallel data processing, and LazyCollection streaming for large file processing in PHP. We integrate import progress monitoring and batch resume after failure using Bus::batch chunks. Our error handling batch logic ensures data integrity.

Get a consultation — write to us, and we'll prepare an architecture for your scenario within a day. Order an audit of your batch process — we'll find bottlenecks and propose optimization.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.