measure search time

[Anon]

Anyone know an easy way to measure search time in a database? And where do you start and stop to measure?

Thanks / Henrik

[[deleted]]

Use microtime() to measure the time it takes:

$query = "SELECT bla FROM bla";
$start_time = microtime();
// Do query
$end_time = microtime();

$aTime = explode(' ',$start_time.' '.$end_time);
echo (($aTime[2]+$aTime[3])- ($aTime[0]+$aTime[1])).' seconds.';

// Fetch data from resultset

[Anon]

thanks, so it isn't standard to measure the time really fetching the fields, just searching?

// Henrik

[[deleted]]

No, because the speed of fetching data depends only on how many records there are, and how big those records are.

That has nothin to do with how long it took to find the records in the first place.

[Anon]

ok, but when we have the $result it's just "loading" left? or?

Sorry for asking so much!

// Henrik

[[deleted]]

What do you mean exactly?

[Anon]

I wonder if just measuring the time of $result says "all" about how fast the db is or if there are more important factors.

When I have the $result-handle, is the only thing that remains, just "loading" of the actual file. Like searching in windows and then clicking on a file when you've found. A bad example but I just want to know if measuring of finding the result is enough to compare efficiency.

/ Thanks

[[deleted]]

When you run a query, most of the time taken is analyzing the query and fetching the data from the table.
This is what puts a load on your database server's CPU.

Once the data is fetched from the tables, sending it to the PHP server is a very simple task that doesn't take much of the CPU.

So it's more important to know how long the query takes than how long it takes to send the data.

Not that the time it takes to send the data is unimportant, but you run into query-speed problems long before you run into 'busy network' problems.

[Anon]

thank you very much for your answers!

// Henrik

[neuromancer]

^_ np