Fastest way to read a 100mb+ file?

ppowell

I'm trying both of these:

if (@filesize(actual_path("$locationPath/" . $self->{$section . '_name'})) > (int)$maxSize) return false;
		 $imgStatArray = @getimagesize(actual_path("$locationPath/" . $self->{$section . '_name'}));

Yet average time comes out to about 30 seconds per 100mb+ file, extremely slow. Is there a faster way to read a very VERY large file?

Thanx
Phil

MarkR

Neither filesize nor getimagesize reads the entire file - they should be constant time independent of the size of the file.

I'm of course assuming that these are local files on the hard drive. If it's a wrapper (e.g. http), forget it.

Also, don't use the @ operator to suppress errors in this way (it will mask genuine problems). Just deal with them sensibly instead.

Mark

ppowell

I found it worked best when I did the comparators in this order:

/*-----------------------------------------------------------------------------------------------------------
			New 7/13/2007 (Friday the 13th!): It appears that filesize() runs the fastest of the three comparators,
			thus should run first, as any file that is too large for this app should not display regardless of its
			identity, otherwise, keep going
		 ------------------------------------------------------------------------------------------------------------*/
		 if (@filesize(actual_path("$locationPath/" . $self->{$section . '_name'})) > (int)$maxSize) return false;
		 if (!preg_match('/^image\//i', @mime_content_type(actual_path("$locationPath/" . $self->{$section . '_name'})))) return false;
		 $imgStatArray = @getimagesize(actual_path("$locationPath/" . $self->{$section . '_name'}));
		 if (!is_array($imgStatArray) || @sizeof($imgStatArray) == 0) return false;

And incidentally, I couldn't find a single way to deal sensibly with warnings thrown for local files that even an is_file() threw a warning as well as false. Ideas?