[eluser]tonanbarbarian[/eluser]
As david said everyone has their own way of doing things
David I would actually suggest that more files is better than fewer.
If you try to cram everything into a single controller, a single model and multiple views you will ultimately be slowing down your site, because PHP will have to parse and process large controller and model files
It also can become harder to maintain the site as you have to hunt through large controller files to find things you need to change
if you split your code into multiple small controllers you can reduce the amount of code that needs to be parsed and processed per request and that should improve performance by being quicker to execute and using less memory.
If your site is ultimately going to have low access rates then it will not be noticeable, however if you try to stress test your site you will notice that it slows down very quickly and uses a lot of resources.
If I have a controller over a few hundred lines of code I try to either split the controller or if I cannot split the controller I move all of the code from the controller into several logical library files and then get the controller to call the libraries instead.
Remember that when you call a page the controller will generally be calling just 1 method from the controller. If the controller has 20 methods in it that is 19 methods that are not needed to service that request.
I am not advocating putting each page into a separate controller, but you need to balance things if you want performance.
The same consideration should be taken for models, however to date I have not ever split a model into several files or even into libraries. all of my models I have just kept as a single file.