On Jan 29, 3:57 pm, chefsmart <moran.cors...@gmail.com> wrote: > When you say "It is taking plenty of time to load Django initially", > what exactly do you mean?
Good question, because depending on what hosting mechanism you are using and how you configure it, Django itself can be lazily loaded on first request, albeit that shouldn't take minutes. If however you are silly enough to use Apache mod_python or mod_wsgi (embedded mode) and first page issues lots of sub requests, all those may go to distinct Apache processes and so every sub request will also incur startup cost. For a complex page this may causes first page to load to take some time. So, question is for OP is whether you have determined for sure whether this is a database issue or whether it is because of how you are trying to host it. Graham > What does initially mean here? Are you > trying to reverse engineer your db using Django's inspectdb? > > Regards. > > On Jan 29, 1:53 am, Saravanan <sarankannan2...@gmail.com> wrote: > > > > > I have Django installed in SUSE Linux with postgres. It is working > > great. Kudos!!!! > > I have an issue. I have total database structure containing more than > > 100million rows. I have partitions and indexes. It is taking plenty of > > time to load Django initially. I meant in minutes. I can take a coffee > > break and a short workout schedule. Is there any ideas/links and other > > resources to speed up the response time (Throughput) > > For you information, I am looking at Cache and DB tunning. Any other > > tricks with Django, anything you are familiar with it? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
