On Wed, Feb 9, 2011 at 11:31 AM, Dev@CB <d...@churchbudget.com> wrote:
> I can't let it go.. the whole "ask a question" and "the return key is > your friend" thing. I thought I was writing an intro blerb to the > moderators... anyway, it was in a little web form box and I just kept > typing. I didn't realize it was going to end up as a post. If I wanted > sarcasm I'd start a conversion with my employer. > > On Feb 8, 12:20 pm, Andres Lucena <andresluc...@gmail.com> wrote: > > On Tue, Feb 8, 2011 at 6:11 PM, Tom Evans <tevans...@googlemail.com> > wrote: > > > On Tue, Feb 8, 2011 at 5:01 PM, Dev@CB <d...@churchbudget.com> wrote: > > >> Tom, why are you discouraging me? > > > > > My intention was not to discourage you; it was to encourage you to ask > > > a sensible question in a legible manner. If you take slight at that, > > > then I have no problem with not corresponding with you further. > > > > I think that is always helpful this text: > > > > http://www.catb.org/~esr/faqs/smart-questions.html > > > > Specially the part: > > > > 1. Try to find an answer by searching the archives of the forum you > > plan to post to. > > 2. Try to find an answer by searching the Web. > > 3. Try to find an answer by reading the manual. > > 4. Try to find an answer by reading a FAQ. > > 5. Try to find an answer by inspection or experimentation. > > 6. Try to find an answer by asking a skilled friend. > > 7. If you're a programmer, try to find an answer by reading the source > code. > > > > And the return key is your friend ;) > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > I'm wondering how a report that takes several hours to run will suddenly run in minutes by moving the application to a more robust server environment. The difference in processors between the two environment 'might' be 2 or 3 times different. That could get you from 2 hours to 1/2 hour. The amount of memory available might also be larger, and that would help. But wouldn't you be better off reviewing the model that creates the report? Have you run that report on the local development server? If you haven't, I'd start there. You could add code to find out where the bottlenecks. -- Joel Goldstick -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
