LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  August 2011

CODE4LIB August 2011

Subject:

Re: memory management for grownups

From:

Joe Hourcle <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 30 Aug 2011 13:14:40 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (51 lines)

On Aug 30, 2011, at 12:56 PM, Ken Irwin wrote:

> I have a feeling it may be time for me to learn some grown-up programming skills, and I hope someone here might be able to help.
> 
> I have a PHP script chewing over a large MySQL query. It's creating a handful of big associative arrays in the process, and punks out after the arrays get to 32MB.
> Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 242 bytes) in analysis.php on line 41
> 
> I'm basically building a big associative array encoding the name of the borrowing institution, the patron type (student,faculty,staff,etc), the item barcode, and the various bits of data we want for each of these items.
> 
> // the first time we see a barcode
>    $stats[$inst][$patron_type][$item_barcode][first] = $date;
>    $stats[$inst][$patron_type][$item_barcode][min] = $renewals;
>    $stats[$inst][$patron_type][$item_barcode][call] = $call_no;
> //subsequent instances of the barcode
>      $stats[$inst][$patron_type][$item_barcode][max] = $renewals;
> 
> Once I've chewed over all  4million records (40MB) , I spit it out into a new MySQL table that has the collated data that I want. Unfortunately this system breaks down when I get to so many millions of records.
> 
> Is there a more efficient way of doing this kind of data transformation? I *could* not keep so much in the big stats array and instead make millions of "UPDATE" calls to the MySQL table, but that doesn't sound like a winning proposition to me. I imagine that I could also increase the memory allotment, but it will eventually get to big too. Or I suppose that I could do it all in chunks - right now I'm parsing the whole raw-data SQL table at once; I could do one institution's data at a time and buy myself some wiggle-room.
> 
> But fundamentally, it seems to me that asking PHP to hold lots of data in an array might not be the most programmerly system; it's just what I've always done.


I don't know how you're getting the data in, so I don't know how much you need to keep in memory during the operation.  I'm also not familiar with how memory-efficient PHP is in general, so I can't recommend changes in that regard, either.

What I can advise is two things -- 

When you mentioned millions of mysql 'UPDATE' calls -- that's rarely efficient.

Instead, write it out to some sort of text file (tab delim, CSV, etc), and then use the 'LOAD DATA ... REPLACE' command:

	http://dev.mysql.com/doc/refman/5.1/en/load-data.html

For this to work, you need to have your primary keys set up correctly, as that's what it'll use for determining if it should do an INSERT or an UPDATE.

...

If you only need a little more than 32MB to deal with (and again, I don't know how memory efficient PHP is; it's possible that 40MB in mysql might be double the space in PHP, or even worse), you can adjust your php.ini file to change the memory limit:

	http://www.php.net/manual/en/ini.core.php#ini.memory-limit

Of course, this is only a stop-gap measure.

...

Personally, I'd go with a mix of these two, plus chunking it out by institution ... you should be able to get a list with a 'SELECT DISTINCT', and then just loop through 'em.


-Joe

ps. See, I made it all the way through the message without commenting that 'PHP' and 'grown-up programming' don't mix ... oh. crap.  Never mind.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager