i checked out the toolbar, and i have a butt load of queries. Not for
everything on the site, but for this particular page there are 300+
queries. They are small and are less than 1ms. I'll try to get this
better :)
However, in regards to Xaviers point, yes I'm sure all DB stuff has
been done.
Hi,
I'm not sure you give enough details or evidences on HttpResponse being slow.
Are you 100% sure that DB access have been made ? Don't forget query sets are
lazy, ie database accesses are not done when you define your queryset.
I got a website with something like 4 (small) DB queries. Without
On Mar 22, 11:41 pm, TheIvIaxx wrote:
> im not about to say my code is prefect :) I'll check out the toolbar
> thing.
>
> my problem though is that timing it to the point where it's completely
> out of my hands is .72 sec and then my browser doesn't get byte #1
> until 1.46 sec. There is a big d
im not about to say my code is prefect :) I'll check out the toolbar
thing.
my problem though is that timing it to the point where it's completely
out of my hands is .72 sec and then my browser doesn't get byte #1
until 1.46 sec. There is a big discrepancy and i'm not sure what is
causing it.
T
On Mar 22, 11:25 pm, TheIvIaxx wrote:
> Not sure whose jurisdiction this falls under, but from my findings,
> this is what i have:
>
> Firebug reports 1.46/.055 sec waiting/downloading. I need the
> "waiting" part to be less than 1 sec.
>
> It looks like sending the response is very fast, but pre
Not sure whose jurisdiction this falls under, but from my findings,
this is what i have:
Firebug reports 1.46/.055 sec waiting/downloading. I need the
"waiting" part to be less than 1 sec.
It looks like sending the response is very fast, but preparing it is
not.
So i investigated as to where th
6 matches
Mail list logo