Re: [SMARTY] yet another benchmark
| From: | Blue Presley | Date: | Fri, 14 Jun 2002 15:14:32 +0000 |
| Subject: | Re: [SMARTY] yet another benchmark | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-4845@lists.php.net to get a copy of this message | ||
having only started programming not too long ago, i might as well be
listening to greek when people start talking about benchmarks and stuff..
but I think that puts me in a unique position to comment.
sure, smarty is a great template program and it's important for a developer
to have something powerful and efficient to work with. but who is going to
end up being the end user? the web surfer. sure.. one page loading at 2.7
secs and another at 3.1 secs, no one is going to notice the difference.. but
if you have an analog clock on the wall watch the seconds hand. if ur
paying attention 1 sec seems like an eternity. and that's what a web surfer
is doing.. paying attention.. be fully aware of when one page comes after
the next and is actually couting the load time in milliseconds in his/her
head.
lets say a site like yahoo is using smarty. sure that 10th of a second
difference is nothing on one page, but it ads up. a person reads the news,
checks email, checks stocks, searches a few times.. goes through 4 or 500
page loads later, the person has sat there about 15 minutes longer than he
would have with a site using a faster template engine.
when i chose to work with smarty, i chose it not because of its plethora of
options and development power.. i chose it b/c after much reasearch it was
hailed as one of the fastest at the time. so speed, for me, is the ultimate
in deciding what engine to work with.
blue
----- Original Message -----
From: "Ben Godfrey" <ben@hypothetical.co.uk>
To: <smarty-general@lists.php.net>
Sent: Friday, June 14, 2002 10:19 AM
Subject: Re: [SMARTY] yet another benchmark
>
> I agree with Ivo. I think that the purpose of the benchmark
> should be to demonstrate to potential users how Smarty will
> perform against it's rivals in a set of realistic situations.
> The user wants to know why Smarty is great for them, which is
> that when you use, it will deliver 1 million pages a minute off
> the back of a Celeron 500, not that it uses PHP style XYZ.
>
> The user shouldn't need to know whether Smarty parses then
> prints, prints then parses or makes toffee. She needs to know if
> it's fast. Also, I think the more technical you get, the more
> you will find yourself taking advantage of Smarty good bits and
> (inadvertently of course) slanting the tests in Smarty's favour.
> I raised the point a while back that the other template system
> authors might want to see the benchmark code, they would
> probably ask that you change the test to favour them.
>
> I think that you need to consider how Smarty will be used and
> test that more. Perhaps test producing 500 versions of one page
> but with different themes or creating a portal page from 25
> sub-templates.
>
> IMHO!
>
> Ben
>
>
> On Friday, June 14, 2002, at 03:00 , Monte Ohrt wrote:
>
> > I still don't see how the benchmark results would be anything
> > conclusive.
> >
> > For instance, Smarty parses/prints in one function. If I run
> > display() 50 times in Smarty, it will parse/compile the first
> > time and execute the compiled template 50 times. Fine. So in
> > FastTemplate, I execute FastPrint() 50 times, which just echoes
> > the template (parsing done). In ModeliXe, the page is cached so
> > all subsequent calls come from the cache.
> >
> > So maybe Smarty takes 3 seconds, FastTemplate takes 2.7 seconds
> > and Modelixe takes 3.1 seconds. What does this mean? One is
> > faster at printing than the other is a parsing/printing? One
> > engine is better than the other because of these numbers? I
> > think the results would be non-conclusive, or even misleading.
> >
> > Ivo Jansch wrote:
> >> Hi,
> >> Monte Ohrt wrote:
> >>> Well this is a tough benchmark to make fair. Some template
> >>> engines combine the parse/print functionality, some do not. So
> >>> a fetch of a template 50 times might be parsing and printing,
> >>> or just printing. ModeliXe uses a cached copy so subsequent
> >>> fetches are just a file fetch.
> >> What is 'fair' in this case anyway? Benchmarks are there for
> >> users to find out which solution is the best for their needs.
> >> The purpose of any template engine is 'to turn a template into
> >> an html file'. How the engine does that is irrelevant. That
> >> Smarty parses the template only once, making it ultrafast,
> >> does not make it an 'unfair' template engine.
> >> Benchmarking template engines without measuring their 'core
> >> business' would be like trying to benchmark formula 1 cars by
> >> just measuring how fast you can put fuel in it. :)
> >> Greetings,
> >> Ivo
> >
> >
> >
> > -- Monte Ohrt <monte@ispi.net>
> > Director of Technology, ispi Inc.
> >
> >
> > -- Smarty General Mailing List (http://smarty.php.net/)
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>
>
> --
> Smarty General Mailing List (http://smarty.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>