We announced that we were going to support Seaside in the next major release of Cincom Smalltalk, and since then, some people have said "you already have a port; what are you bringing to the table?"

Well, Glorp (persistence in an RDBMS) is one thing - but scaling is another. I downloaded WAPT, and ran a few simple tests. I only have the demo version, so I was limited to simulating 20 users. I should also mention that I'm running Seaside on my MacBook Pro, and using Windows in Parallels to run the tests.

With that out of the way, here's what I tested: Seaside 2.8 in Squeak (using the "one click experience" image), Seaside 2.7 on VW, and Seaside 2.8 on VW - the latter required the under development release that's coming. Here's a summary of what I got:

Looking at that, I think you can see one major benefit of having us actively work on Seaside; by rationalizing the server, we've improved the scalability a lot. The test script I used in WAPT was pretty basic - launch the Counter demo, and then just increment to 4, and decrement back down to 0.

Also relevant is this: In Seaside 2.7 on VW, pages per second started off at 34, and then dropped to 10 by the end of the one minute test. Squeak dropped from 50 to 45.5, which is pretty stable. VW 7.6 with Seaside 2.8 started at 81, and dropped to 79.5 - which is even more stable.

Technorati Tags: smalltalk, cincom smalltalk, web2.0, scaling