Lots of little MVCs or just one MVC?

ok… so say you’re building a website… with a few different simple applications. a slideshow, a mp3 player, and whatever else…

I’m completing my first MVC website, and I have one main question.

do i use one large model for the data of each individual application, or do i use many smaller models to hold the data specific to that application.

Of course that one sounds better… keeping the apps separate, and cleaner… but then what if i want the views to respond to events from another model??

do i “nest” complete mvc apps inside one large mvc app? is that the normal practice… thanks for any help.