[Seaside] Performance

Davide Varvello d.varvello at quinary.com
Thu May 19 14:29:04 CEST 2005


 
> Message: 5
> Date: Thu, 19 May 2005 00:30:29 +0200
> From: Avi Bryant <avi.bryant at gmail.com>
> Subject: Re: [Seaside] Performance
> To: "The Squeak Enterprise Aubergines Server - general discussion."
> <seaside at lists.squeakfoundation.org>
> Message-ID: <ad69ab6905051815307510dfbb at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On 5/18/05, Davide Varvello <d.varvello at quinary.com> wrote:
>> Hi All,
>>  Have you some data about Seaside's performance?
> 
> On Squeak or VW?  On what kind of a machine?  Under what kind of load?
>  Doing what?

Hi Avi,
Your questions are right. Actually I'm doing some spikes on Seaside, on
continuations, on the ease of development compared to traditional coding in
a web context. At the moment, I'm interested to have a general opinion, so
your considerations below are enough for me.
Thanks
 Davide

> By and large, Seaside hasn't been optimized for performance, or for
> resource usage in general - it's been optimized for developer speed.
> It would not surprise me if a comparison between Seaside and <insert
> your favorite web framework here> ended up with Seaside lagging,
> perhaps by quite a bit, in memory footprint or requests per second.
> And if you're trying to build the next Yahoo, you probably won't use
> Seaside, for that reason.
> 
> On the other hand, there are plenty of Seaside apps out there in
> production use that do just fine, most with total users in the 10-1000
> range and concurrent users in the 1-50 range.  If you need more than
> that, you can hopefully afford to throw some hardware at the
> problem...
> 
> Avi
> 



More information about the Seaside mailing list