sage-
From: symfony-devs@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Jonathan H. Wage
Sent: Monday, May 14, 2007 9:52 AM
To: symfony-devs@googlegroups.com
Subject: [symfony-devs] Re: Sfguard improve and system optimization
Hmm, it depends on your infrastructure. If you have one small we
Great, we are working using propel, but we are trying to maintain queries
between 6 and 2, exceptionally 8. We use a lot of joins tough.
Thank you again!
On 5/14/07, Jonathan H. Wage <[EMAIL PROTECTED]> wrote:
>
>
> Hmm, it depends on your infrastructure. If you have one small web server
> with we
Hmm, it depends on your infrastructure. If you have one small web server
with web and db server on one machine, and lots of traffic, with a high
query count per page, then your db server will get backed up and it will
be slow.
I have had sites once upon a time with very high query counts, 50-1
Great example, thanks!
what do you think about the theoricall maximum tolerable number of queryes
per request?
On 5/14/07, Jonathan H. Wage <[EMAIL PROTECTED]> wrote:
>
>
> I think it should be stored in the instance of the user for each
> request, rather than in the session. In large sites with
I think it should be stored in the instance of the user for each
request, rather than in the session. In large sites with lots of users,
the memory usage for sessions could grow to be too large. Since each
request has only one instant of the sfUser class then you can store the
guardUser, permi
