It really just depends on how you're accessing the data. I tend to optimize
for developer simplicity first, and then go in and adjust/split/modify code
as needed when performance isn't where it needs to be for whatever
application I'm working with.

The case where multiple models might work a little better than fewer, larger
models is where you find yourself with either a lot of sparse data (some
significant portion of the model being null or empty), or the need to
consistently edit just a small portion of the data (one bit of metadata gets
updated a lot, the rest of the information doesn't).

But practically, I'd recommend building your app so that it makes the most
sense to you, and then seeing how the performance rolls out. Worrying about
"that might make the performance bad" from the very beginning isn't usually
a good idea.

-joe

On 12/14/06, Austin Govella <[EMAIL PROTECTED]> wrote:
>
>
> I'm new to Django, so I was looking for some advice on good model and
> app design and on how that affects performance.
>
> My first app has nine models, and after working with it for a bit, it
> seems like it's actually two apps: one for meta data and another for
> content management.
>
> Are there any rules of thumb for when you should separate out some
> functionality into its own app? Is there a certain number of models
> that would suggest you probably have more than one app?
>
> Is there any impact on Django's performance? I.e. is an app with four
> models faster than an app with 20?
>
> If I'm importing models from one app into another, is that
> faster/slower than just having all the models in one app?
>
> (In my case, I'd move the four meta data models to a separate app and
> import just one of them into the content management app. Is this
> actually slower than just keeping all the models in one single app?)
>
>
>
> Thanks,
> --
> Austin Govella
> Thinking & Making: IA, UX, and IxD
> http://thinkingandmaking.com
> [EMAIL PROTECTED]
>
> >
>


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to