Dr. Tarique Sani wrote:
Not to sound like a prick but 400,000 page views are not much for a
typical 3+1 configuration. Given your estimate of higher performance
you say you will reach about 1.2 million page views on the same setup
which again makes me want to know your hardware configuration.
Hi bgmill
The decision to use 3+1 straight off the bat was mainly due to the need
for handling rapid expansion
Thanks for that info, much appreciated. One more question though, when
you say 3+1 do you mean a cluster of 3 database servers and one web
server?
Regards,
Langdon
On 12/27/06, Langdon Stevenson [EMAIL PROTECTED] wrote:
Thanks for that info, much appreciated. One more question though, when
you say 3+1 do you mean a cluster of 3 database servers and one web
server?
I think he said 3 web servers + 1 MySQL, MySQL server is probably a
master and handles
On 12/27/06, bgmill [EMAIL PROTECTED] wrote:
Thanks for your reply
Firstly, I don't claim to be a hardware guru, and my estimations are
purely based on brief conversations with the techs who run the servers.
So with that in mind... all the machines are dual xeon 2.8GHz with 2Gb
of memory.
Hi Woodsman
Caching, and lots of it, and DB clustering/replication are definitely
the quickest fixes.
Caching (both on the server and the client side) are certainly looking
good for my current project. I haven't used Cake's view caching yet,
but am definitely going to look into it. I can
That's a dream!
http://www.mytechsky.com
On 12 24 , 3 10 , keymaster [EMAIL PROTECTED]
wrote:
.. just dreaming, but..
If one wanted to use cake to build an app which is scalable to the
extreme, ie. flickr.com or yourtube.com or myspace.com, how would you
do it?
Would you just separate out
It's an interesting question. I am working on an application that (if
it works out for the client) may grow to support thousands of users with
requirements for high availability.
If it ever grows that far, then I expect that we will need to redevelop
at least some parts of the application
On 12/24/06, keymaster [EMAIL PROTECTED] wrote:
.. just dreaming, but..
If one wanted to use cake to build an app which is scalable to the
extreme, ie. flickr.com or yourtube.com or myspace.com, how would you
do it?
http://www.onjava.com/pub/a/onjava/2003/10/15/php_scalability.html
Langdon Stevenson [EMAIL PROTECTED] wrote:
I think that I would likely just replicate the entire application
across multiple web servers, and hand out the requests in a round
robin to the web servers.
Or maybe FastCGI's load balancing?
I would be very interested to hear anyone else's
, be cool, and share your knowledge.
BAKE ON!
-Mensaje original-
De: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] En nombre
de Langdon Stevenson
Enviado el: Domingo, 24 de Diciembre de 2006 05:33 a.m.
Para: cake-php@googlegroups.com
Asunto: Re: how would you scale a cake app?
I would
A simple way to let a webapp scale is to moved session's and db's data
to cookies as much as possible.
olivvv
Nimrod A. Abing wrote:
On 12/24/06, keymaster [EMAIL PROTECTED] wrote:
.. just dreaming, but..
If one wanted to use cake to build an app which is scalable to the
extreme, ie.
I'm running a cake app on 3 webservers (round robin dns) and 1 mysql
server right now, traffic yesterday was around 200,000 uniques and
400,000 page views.
Caching is being used on some of the heavier hit controllers but all in
all, load is minimal across the board -- we could easily handle 2
On Dec 24, 4:01 pm, Mariano Iglesias [EMAIL PROTECTED]
wrote:
CakePHP is a framework that allows you to
easily develop your application thinking about scalability all the way, so
take advantage of that.
I understand how the MVC separation and strict coding conventions make
maintainability
nombre
de bgmill
Enviado el: Domingo, 24 de Diciembre de 2006 01:29 p.m.
Para: Cake PHP
Asunto: Re: how would you scale a cake app?
I'm running a cake app on 3 webservers (round robin dns) and 1 mysql
server right now, traffic yesterday was around 200,000 uniques and
400,000 page views
PROTECTED] En nombre
de keymaster
Enviado el: Domingo, 24 de Diciembre de 2006 01:21 p.m.
Para: Cake PHP
Asunto: Re: how would you scale a cake app?
I understand how the MVC separation and strict coding conventions make
maintainability easier as the application gets larger (in terms of
lines of code
I may well write an article for the bakery after the holiday season -
are there any other high traffic sites known to be using cake?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP group.
To post to this
Hi bgmill
Sounds like you have a good system/site there. Can you tell me what
sort of hardware it is running on?
Regards,
Langdon
I'm running a cake app on 3 webservers (round robin dns) and 1 mysql
server right now, traffic yesterday was around 200,000 uniques and
400,000 page views.
Caching, and lots of it, and DB clustering/replication are definitely
the quickest fixes.
One minor point is to avoid using Cake's multi join SQL, which (I
believe) can literally add thousands of queries when a single one would
do.
In such cases, don't be afraid to use query() instead of
Also, check if Cake doesn't get more than you need, and consider dynamic
unbinding where you don't need as much info as you get using default models'
options.
--
Olexandr Melnyk,
http://omelnyk.net/
--~--~-~--~~~---~--~~
You
On 12/24/06, bgmill [EMAIL PROTECTED] wrote:
I'm running a cake app on 3 webservers (round robin dns) and 1 mysql
server right now, traffic yesterday was around 200,000 uniques and
400,000 page views.
What kind of hardware are you using?
Not to sound like a prick but 400,000 page views are
.. just dreaming, but..
If one wanted to use cake to build an app which is scalable to the
extreme, ie. flickr.com or yourtube.com or myspace.com, how would you
do it?
Would you just separate out the db server and replicate the rest on
identical nodes in a cluster? Would you break up the app
21 matches
Mail list logo
