CI-based Web Sites Performance

[eluser]tonanbarbarian[/eluser]
ok i sort of agree with lewis

i am thinking the reason that the db->result type functions were created were for convenience. it makes it easier to use methods to move back and forward amongst the records

while it does mean you have to parse through a loop twice there are things you can do to improve performance

for example

Code:

foreach ($query->result() as $row) ...

is fairly slow because it has to run the function on each iteration of the loop
use

Code:

$rows = $query->result();
foreach ($rows as $row) ...

instead

how much slower is it to have to process the loop twice though?
well that does depend on how many records you are processing.
if you are using a paginated list you wall always be limiting the number of records you retrieve.
So if it is 5, 10, 20, 50 or even 100 records in the result set then it is going to be very fast because the loop size is small and I would not worry about this as an issue.

If you are not using limits and you are having to pass 1000's of records then the extra processing may be noticable, but this is not something that happens often, and you could consider breaking your process into batches anyway and refreshing the pages in between.

having said all of this I have expressed a desire before to have something like

Code:

$this->query->fetch_object();
$this->query->fetch_array();

each of which just gets the next record but does not do any of the other processing that CI normally uses to "cache" the result data