I agree with this too. And about the budget is ok, because we've
spending some company resources in the building of that with no limit
of time/budget.
It's enough to have the rest of the resources working on our clients
and some of us on the development of this app.
After completion and site work
well, look we are at analysis step yet.
it's a community website with a development size like DeviantArt.com
but more oriented to musicians.
I think it could have a minimum of 10k unique visits daily at start.
And after some marketing it will growth.
On Jan 3, 1:59 am, "Dr. Tarique Sani" <[EMAI
On 1/3/07, Chris Hartjes <[EMAIL PROTECTED]> wrote:
Just Build Something, Damnit and worry about fixing any performance issues
later.
Agreed - but a word of caution the "later" should be much before the
site goes live, clients don't take kindly to server meltdowns within
hours of going live.
On 1/2/07, Leandro Ardissone <[EMAIL PROTECTED]> wrote:
I'm starting a big PHP application and planning to use Cake as the
framework.
Nice to know this, I like big applications - but do elaborate on how
big this is going to be...
How many tables? What is the expected traffic?
Tarique
--
===
I'd like to add that I agree whole heartedly with Chris, but one thing
you should consider is how you are going to use caching, specifically
with your views. From my experience with using Cake and building other
large applications this is the first place you can gain large
performance improvemen
great..
thanks guys..
I'll follow the Chris steps (which don't differs too much from my
original thoughts) keeping in mind your others suggestions.
happy new year
--
Leandro
On Jan 2, 6:52 pm, "pmjones" <[EMAIL PROTECTED]> wrote:
Chris, you are exactly right. Building and benching in iterat
Chris, you are exactly right. Building and benching in iterations is
reasonable and realistic.
Having said that, when you get to point where you **do** need to
benchmark in order to improve performance, you will need to know the
limits of the framework. No matter how much optimizing you do in
On 1/2/07, Chris Hartjes <[EMAIL PROTECTED]> wrote:
... Premature optimization lies on the path to developer madness...
My thoughts exactly. I think I have said something similar in post before.
One being after I changed the code to use lazy loading.
--
/**
* @author Larry E. Masters
* @var s
Well said Chris, I should bookmark this post for future reference ; ).
-- Felix Geisendörfer aka the_undefined
--
http://www.thinkingphp.org
http://www.fg-webdesign.de
Chris Hartjes wrote:
On 1/2/07, Leandro Ardissone <[EMAIL PROTECTED]> wrote:
Thanks Dinh,
really gr
On 1/2/07, Leandro Ardissone <[EMAIL PROTECTED]> wrote:
Thanks Dinh,
really great article!
thank you.. it will help me in the benchmarking.
Just to inject some sanity into what should be a very interesting
thread, I urge anyone building an application to simply BUILD IT and
worry about the p
For the most part, as far as optimizations go, if you set DEBUG to 0,
Cake will take care of most production optimizations for you. A few
other things you can do are move the .htaccess rules into httpd.conf,
and make sure your DocRoot is pointed at the webroot folder.
As far as security, you sh
Thanks Dinh,
really great article!
thank you.. it will help me in the benchmarking.
I guess also some other aspects I need to take into account.
Regards,
Leandro
On Jan 2, 3:31 pm, Dinh <[EMAIL PROTECTED]> wrote:
Performance would be certain thing you need to take into account. A
well-known
Performance would be certain thing you need to take into account. A
well-known PHP developer's article may be of interest:
http://paul-m-jones.com/blog/?p=238
Dinh
On 1/3/07, Leandro Ardissone <[EMAIL PROTECTED]> wrote:
Hi,
I'm starting a big PHP application and planning to use Cake as the
f
Hi,
I'm starting a big PHP application and planning to use Cake as the
framework.
But I'm interested on know resources about big php applications
developments and things to keep in mind on the design process,
analysis, and security stuff.
Anyone know where can I start to research about that?
I
14 matches
Mail list logo
