Friday, October 1, 2010

Re: Odd DESCRIBE issue

On Fri, Oct 1, 2010 at 8:16 PM, j.blotus <j.blotus@gmail.com> stated:
> DESCRIBE is taking what, 0-1ms each?

After the first time, yes, I assume due to MySQL caching. If you read
what I posted, I was showing DESCRIBE queries 57 - 63. You can safely
assume that those same tables had already been described before.

But that's not the point. The point is that the framework is making
repeated queries for no apparent reason. And, for the majority of the
pages, the describe statements take up at least twice as much time as
the remaining queries. And for my largest query group, the combined
time of the DESCRIBEs take up as much time as pulling data for one
member from nine different tables.

Why would any software have to DESCRIBE the same table three or more
times in a row? I'm not aware of any special setting we've done to
cause this. We don't have any special modifications to the core,

On Fri, Oct 1, 2010 at 8:23 PM, Dave Maharaj <me@davemaharaj.com> wrote:
> I thought DECRIBE is when (debug, 2) ?

I thought so to, and ignored it for some time after I put the
developed system live. But when I got calls about page loads taking
too long, I turned on query logging and found it was still running
DESCRIBEs

> And to increase the time between DESCRIBE there is a way to change it from
> the set 10 second or what not to whatever time you want. So it describes
> every min rather than every request.
>
>
> open configure.php in cake/libs/
> locate the function __loadBootstrap
> inside this function locate the following
> if (Configure::read() >= 1) {
> $duration = '+10 seconds';
> } else {
> $duration = '+999 days';
> }
>
> Change the '+10 seconds' according to your requirement, say you want to
> describe a query every 1 minute, you would change it to
> if (Configure::read() >= 1) {
> $duration = '+1 minute';
> } else {
> $duration = '+999 days';
> }
>
> No?

I'll have to try that after the weekend. I appreciate the lead: I
didn't care to look into the core because I didn't want people blaming
modifications on the issue, and I didn't want to have to fix a popular
framework to make it work as expected.

--
Jack Timmons
@_Codeacula

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en

No comments: