Performance loss large Database

[eluser]Unknown[/eluser]
Hi. Thanks for the replies.

The problem is, that each tour has like up 30 details segment. So a join would produce a result with the whole tourdata for 30 times, which isn't needed and would have to be sorted out afterwards.I don't think the query itself is the problem. I think it is the transfer between model->controller->view where the whole thing is looped several times.

Yes there are several indexes. As i said: The same database is beeing used by the "old version" which is performing very well.

The view is loaded pretty basic. The tourarray is returned to the controller where the view is loaded
$this->load->template('umlauf',$data);
the load->template is only including header and footer so I don't have to do it on each controller.

I will check out the unbuffered->row

Thanks so far.