News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Brian Moon's Blog:
in_array is quite slow
June 06, 2008 @ 09:36:47

Brian Moon had a problem - one of his cron jobs was lasting for much longer (hours!) than it should have been. He tweaked, tested and debugged the script and finally came down to a call to in_array, something he comments on as being "quite slow".

See, this job is importing data from a huge XML file into MySQL. After it is done, we want to compare the data we just added/updated to the data in the table so we can deactivate any data we did not update. [...] We then compared the two arrays by looping one array and using in_array() to check if the value was in the second array. [...] So, that was running for hours with about 400k items. Our data did not contain the value as the key, but it could as the value was unique.

He method, replacing the in_array call that had to do a full array scan for each time through the loop with an isset/unset combo on the unique key, changed the execution time down from about 4 hours to 0.8 seconds.

1 comment voice your opinion now!
inarray compare array unset isset unique key execution time


blog comments powered by Disqus

Similar Posts

Jonathan Snook's Blog: CodeIgniter vs. CakePHP

OurBlogLog.com: Joomla vs Drupal , The Sad Truth

Stijn Leenknegt's Blog: [PHP6] function-return-array idea!

Secunia.com: PHP "glob()" Code Execution Vulnerability

Felix Geisendorfer's Blog: Handling inline links to dynamic resources


Community Events





Don't see your event here?
Let us know!


install community framework version symfony opinion language release package podcast interview update application introduction series security laravel voicesoftheelephpant composer library

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework