[TYPO3] [Typo3] How large of website can typo3 handle?

[Dennis Cheung]

Something I have forgot.

http://typo3.org/development/articles/testing-and-tuning-typo3-performance/page/4/

It do "ab" on "same page" alot to check the performance.
But, it still using sql cache inside mysql.
I really want to know the "random access" performance, not a "cached"
or "burst" performance.

>My best guess is on a single server, like 1 2.4Ghz/1GB ram SCSI disks
you will hit the limit at 20.000 pages.

you means 20k pages? how about the page loading time? it is inside 1s
for the HTML content?


Dennis

On 1/5/06, Dennis Cheung <hkdennis2k at gmail.com> wrote:
> Thanks guys,
>
> I have read
> http://typo3.org/development/articles/testing-and-tuning-typo3-performance/
> before.
> I really wanted to ask is, what else, any else, I can do "inside
> typo3" other than tweaking "outside typo3". Anything or Nothing??
> (even rewrite source code)
>
> quote from the document
> ...Watch out for performance killer extensions from TER by constantly
> testing their impact on performance.
> How should I know who is/are the "performance killer"?
>
>
> I have read some document, I can categorize the skill into 2 type.
>  1. content cache, page cache, proxy cache
>  2. php optimizer / mysql/apache tweaking
> any else?
>
>
> Three more question,
> http://typo3.org/development/articles/the-mysteries-of-chash/
> http://typo3.org/development/articles/the-mysteries-of-chash/page/3/
>
> If I have a plugin using "&no_cache=1 (slow)"
> how to rewrite it into "USER_INT (medium)" or "&cHash (fast)"
> I didn't found any live example.
>
> What is "no_cache" really mean?
>  do not try reading from cache?
>  do not write to cache?
>  page cache? template cache?
>  it is cache static page content?
>
>
> should mysql installed on same machine(reduce network delay)
> or install them on two machines(if total cost are equals)
>
> I feel I have asked so many stupid question. Am I?
>
> thanks,
> Dennis
>
>
> On 1/5/06, Steffen Müller <steffen at mail.kommwiss.fu-berlin.de> wrote:
> > On 01/04/2006 11:44 PM Ries van Twisk wrote:
> >
> > >
> > > Also at some point page generation is going to be come a problem.
> > > - When you have 20.000 pages and page generation time is long (at my
> > > site +5 seconds) then indexing
> > > such a thing is a problem, for example by google etc... Means like that
> > > indixing this takes up a complete day to complete. (27 hours) saturating
> > > your server (I know google is smart and spread the load... but there is
> > > more then just google).
> >
> > you can always use a proxy in front of your typo3, even on a single
> > server. Frontend output will then be lightning fast without producing
> > much load, if you don't have massive dynamic content. No problem with
> > googlebots, not even with slashdot, if you temporariliy disable search
> > and other non-cachable content while being under "attack"...
> >
> > --
> > cheers,
> > Steffen
> > _______________________________________________
> > TYPO3-english mailing list
> > TYPO3-english at lists.netfielders.de
> > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
> >
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>