7

I'm running into an issue when trying to insert ~20K records into my DB. I notice that even though I'm echoing inside my foreach loop, I'm not getting anything outputted in the command line. Instead, I get an error after inserting ~9440 records relating to...

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 91 bytes) in /Users/me/Sites/Laravel/database/connection.php on line 293

Here is my code (tried using both Eloquent and Fluent):

<?php

class Process_Controller extends Base_Controller
{
    public function action_migrate()
    {
        $properties = DB::table('raw_properties')->get('id');
        $total = count($properties);

        foreach ($properties as $x => $p) {
            $r = RawProperty::find($p->id);
            $count = $x + 1;

            $prop_details = array(
                'column' => $r->field,
                // Total of 21 fields
            );

            DB::table('properties')->insert($prop_details);

            echo "Created #$count of $total\n";
        }
    }
}
Karl Hill
  • 12,937
  • 5
  • 58
  • 95
csm232s
  • 1,660
  • 4
  • 32
  • 60

3 Answers3

34

The accepted answer is fixing the symptom rather then the problem. The problem is the Laravel query log (in memory) is eating all your RAM when you execute such a large # of queries. See the answer here: https://stackoverflow.com/a/18776710/221745

Or, in brief, turn off query logging via:

DB::disableQueryLog()

Before executing 20k queries

Community
  • 1
  • 1
Erik
  • 20,526
  • 8
  • 45
  • 76
0

This error depicts that your PHP script has exhausted memory limit due to insufficient memory allocated for script.

You need to increase memory_limit using the ini_set function e.g ini_set('memory_limit','128M');

Rubin Porwal
  • 3,736
  • 1
  • 23
  • 26
  • 3
    I just hit this problem to, increasing the memory limit is a quick fix. A much better solution is to turn off query logging as recommended by @Erik below – th3hamburgler Oct 14 '13 at 17:00
0

I did the DB::disableQueryLog() and continued to get the error. I ended up Pausing Telescope from recording the queries. You can do this from the telescope web interface > queries > Click the Pause Icon.

Richard Dev
  • 1,110
  • 7
  • 21