Comments on: Know what to use where http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/ Just another WordPress weblog, or something like that Sun, 16 May 2010 16:52:11 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Jeremy Privett http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/comment-page-1/#comment-2693 Jeremy Privett Fri, 12 Jan 2007 13:23:17 +0000 http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/#comment-2693 <blockquote>Oh, and 19 / 24 = .79, 1.65 / 2 = 0.825, so the relative difference is about the same, don’t you think?</blockquote> I forgot to comment on this, but yeah, you're right. That's what I get for doing this after only having a few hours of sleep. :P

Oh, and 19 / 24 = .79, 1.65 / 2 = 0.825, so the relative difference is about the same, don’t you think?

I forgot to comment on this, but yeah, you’re right. That’s what I get for doing this after only having a few hours of sleep. :P

]]> By: Jeremy Privett http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/comment-page-1/#comment-2692 Jeremy Privett Fri, 12 Jan 2007 13:20:44 +0000 http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/#comment-2692 For the test machine, I used my development laptop. A Toshiba Satellite with an Intel Core Duo processor clocking in at 3.2 Ghz with 2 GB of RAM. I'm actually <strong><em>surprised</em></strong> that I got that kind of result, considering how loaded down my laptop is constantly with all of my development tools. Apache / MySQL & IIS / MSSQL are always running, and I usually have both Zend Studio and Visual Studio open at the same time. Not to mention multiple browsers. Microsoft Word, OneNote, and Outlook ... You get the idea. :P For the test machine, I used my development laptop. A Toshiba Satellite with an Intel Core Duo processor clocking in at 3.2 Ghz with 2 GB of RAM.

I’m actually surprised that I got that kind of result, considering how loaded down my laptop is constantly with all of my development tools.

Apache / MySQL & IIS / MSSQL are always running, and I usually have both Zend Studio and Visual Studio open at the same time. Not to mention multiple browsers. Microsoft Word, OneNote, and Outlook … You get the idea. :P

]]> By: Jory http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/comment-page-1/#comment-2691 Jory Fri, 12 Jan 2007 11:44:03 +0000 http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/#comment-2691 True, the effects of isset() and array_key_exists() is somewhat different, I should have mentioned that. But as I, and most others, will normally want to know if a $var set to <em>something usefull</em>, which NULL really isn't, you'll just want to use the faster one anyway. Thanks for the heads-up though, I'll add a note about it. :) Oh, and 19 / 24 = .79, 1.65 / 2 = 0.825, so the relative difference is about the same, don't you think? ;) (btw, with times like that, was are you testing on? :P ) True, the effects of isset() and array_key_exists() is somewhat different, I should have mentioned that. But as I, and most others, will normally want to know if a $var set to something usefull, which NULL really isn’t, you’ll just want to use the faster one anyway. Thanks for the heads-up though, I’ll add a note about it. :)

Oh, and 19 / 24 = .79, 1.65 / 2 = 0.825, so the relative difference is about the same, don’t you think? ;)
(btw, with times like that, was are you testing on? :P )

]]> By: Jeremy Privett http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/comment-page-1/#comment-2685 Jeremy Privett Fri, 12 Jan 2007 01:21:44 +0000 http://blog.jorygeerts.com/2007/01/11/know-what-to-use-where/#comment-2685 Couple of things to take note of: First, isset() is a language construct and not a function. As such, it's inherently going to be faster than any related function ever could be. Second, depending on the functionality you're looking for, array_key_exists() might be a better choice. If you check out the <a href="http://www.php.net/manual/en/function.array-key-exists.php" rel="nofollow">manual page for array_key_exists()</a> there's a section defined specifically to point out the differences between it and isset(). You'll want to use this to judge which method is most appropriate to use, based on your situation. 9 times out of 10, isset() has been perfect for <strong><em>my</em></strong> personal needs, though. As far as the benchmarks go, the margin was considerably smaller for me, because the overall script execution time was only about 2 seconds, but array_key_exists() filled over 1.65 of those 2 seconds. Couple of things to take note of:

First, isset() is a language construct and not a function. As such, it’s inherently going to be faster than any related function ever could be.

Second, depending on the functionality you’re looking for, array_key_exists() might be a better choice. If you check out the manual page for array_key_exists() there’s a section defined specifically to point out the differences between it and isset(). You’ll want to use this to judge which method is most appropriate to use, based on your situation. 9 times out of 10, isset() has been perfect for my personal needs, though.

As far as the benchmarks go, the margin was considerably smaller for me, because the overall script execution time was only about 2 seconds, but array_key_exists() filled over 1.65 of those 2 seconds.

]]>