Nice find!
If you turn debugging on for "django.db.backends", it will show you what
SQL queries are being issued, and the time taken for each.
LOGGING['handlers']['console'] = { 'level':'DEBUG', 'class':
'logging.StreamHandler' }
LOGGING['loggers']['django.db.backends'] = { 'handlers':['console
ff: AW: problem with timeout
Thanks, that does sound like a better idea and now that i think about it i saw
this behaviour on many other webinterfaces already…don’t know why i didn’t
think about that ☺
However I’ve noticed that it’s not the query that is taking so long, it’s the
processing
groups.com
Betreff: Re: problem with timeout
On Mon, Dec 17, 2012 at 7:34 PM, Szabo, Patrick (LNG-VIE)
mailto:patrick.sz...@lexisnexis.at>> wrote:
Hi,
I have an operation that takes about 10 minutes to befinished. It takes that
long because our DB is pretty big.
This produces a timeout.
On Mon, Dec 17, 2012 at 7:34 PM, Szabo, Patrick (LNG-VIE) <
patrick.sz...@lexisnexis.at> wrote:
> Hi,
>
> I have an operation that takes about 10 minutes to befinished. It takes
> that long because our DB is pretty big.
> This produces a timeout.
>
> I have tried so set the timeout in apache highe
you could optimize the database (creating indexes, putting in memory, using
a ssd etc)
you can run the process in backgorund
On Mon, Dec 17, 2012 at 1:34 PM, Szabo, Patrick (LNG-VIE) <
patrick.sz...@lexisnexis.at> wrote:
> Hi,
>
> I have an operation that takes about 10 minutes to befinished. It
Hi,
I have an operation that takes about 10 minutes to befinished. It takes that
long because our DB is pretty big.
This produces a timeout.
I have tried so set the timeout in apache higher but it seems that apache is
not taking this directivejust keeps timing out after 300 seconds.
Is the
6 matches
Mail list logo
