So this is what I get for a simple login with one select query to compare
the email and password. This is not going to scale well to a high traffic
website What is the deal with all the additional queries to the database?
2010-04-08 13:03:41.448 PDT,"postgres","2_db",
4422,"192.168.1.130:4179",4bbe35f3.1146,130,"idle",2010-04-08 13:00:51
PDT,4/170,0,LOG,00000,"statement: SELECT ""Account"".""email"" AS
""Account__email"" FROM ""accounts"" AS ""Account"" WHERE
UPPER(email)=UPPER('a...@mail.com') LIMIT 1",,,,,,,,
2010-04-08 13:03:41.449
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,131,"SELECT",2010-04-08
13:00:51 PDT,4/0,0,LOG,00000,"duration: 1.098 ms",,,,,,,,
2010-04-08 13:03:41.454
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,132,"idle",2010-04-08
13:00:51 PDT,4/171,0,LOG,00000,"statement: select oid,typname from
pg_type",,,,,,,,
2010-04-08 13:03:41.456
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,133,"SELECT",2010-04-08
13:00:51 PDT,4/0,0,LOG,00000,"duration: 1.817 ms",,,,,,,,
2010-04-08 13:03:41.526
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,134,"idle",2010-04-08
13:00:51 PDT,4/172,0,LOG,00000,"statement: BEGIN;",,,,,,,,
2010-04-08 13:03:41.527
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,135,"BEGIN",2010-04-08
13:00:51 PDT,4/172,0,LOG,00000,"duration: 0.620 ms",,,,,,,,
2010-04-08 13:03:41.530
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,136,"idle
in transaction",2010-04-08 13:00:51 PDT,4/172,0,LOG,00000,"statement:
ROLLBACK;",,,,,,,,
2010-04-08 13:03:41.530
PDT,"postgres","2_db",4422,"192.168.1.130:4179",4bbe35f3.1146,137,"ROLLBACK",2010-04-08
13:00:51 PDT,4/0,0,LOG,00000,"duration: 0.605 ms",,,,,,,,
On Thu, Apr 8, 2010 at 12:55 PM, altermod <localmotion...@gmail.com> wrote:
> The Begin/Rollbacks are still showing up in the Postgres log. There are
> still a ton of useless selects and I'm not even doing a query.
>
> On Thu, Apr 8, 2010 at 12:33 PM, Jeremy Burns <jeremybu...@me.com> wrote:
>
>> What happens if you place <code> var $persistModel = true; </code> in your
>> app_controller?
>>
>> Jeremy Burns
>> jeremybu...@me.com <jeremybu...@mac.com>
>>
>>
>> On 8 Apr 2010, at 20:30, altermod wrote:
>>
>> John,
>>
>> I have set my debug to zero and am looking at the database logs and I
>> still see alot of begin / rollback / set queries on the database. This is
>> troubling to see that all these transactions occur for a simple login with
>> only 1 query. Do you have any idea whether or not all these excessive
>> transaction/queries can be removed?
>>
>> I was planning to use cake for a large high traffic website but am
>> reconsidering this after seeing the load on the postgres database for a
>> simple login and redirect that uses only 1 select query.
>>
>> Thanks.
>>
>> Adam
>>
>> On Thu, Apr 8, 2010 at 10:41 AM, John Andersen
>> <j.andersen...@gmail.com>wrote:
>>
>>> My question is, have you turned debug off?
>>>
>>> If you are still developing the application, then you probably will
>>> always have debug turned on, and thus you will always see the schema
>>> information.
>>>
>>> When you are ready to realize your application in a production
>>> environment, you must turn debug off, and the schema information will
>>> only be read the first time (CakePHP team, please correct me if I am
>>> wrong!).
>>>
>>> So as long as you are developing the application, the schema
>>> information will sometimes be read again.
>>> Enjoy,
>>> John
>>>
>>> On Apr 8, 7:31 pm, altermod <localmotion...@gmail.com> wrote:
>>> > Hi John,
>>> >
>>> > It still seems to be calling those queries every time I go to the login
>>> > page. I don't even run any db queries of my own on the login page. When
>>> is
>>> > it going to start caching? Or do I have to change a setting in the
>>> config?
>>> > I'm running Postgres 8.3.
>>> >
>>> > Thanks.
>>> >
>>> > Adam
>>> >
>>> [snip]
>>>
>>> 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+unsubscr...@googlegroups.com<cake-php%2bunsubscr...@googlegroups.com>For
>>> more options, visit this group at
>>> http://groups.google.com/group/cake-php?hl=en
>>>
>>> To unsubscribe, reply using "remove me" as the subject.
>>>
>>
>>
>> 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+unsubscr...@googlegroups.com For more options, visit this group
>> at http://groups.google.com/group/cake-php?hl=en
>>
>>
>> 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+unsubscr...@googlegroups.com<cake-php%2bunsubscr...@googlegroups.com>For
>> more options, visit this group at
>> http://groups.google.com/group/cake-php?hl=en
>>
>
>
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+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
