[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-smalltalk] web serving speed thoughts

From: Paolo Bonzini
Subject: [Help-smalltalk] web serving speed thoughts
Date: Sat, 03 Oct 2009 12:34:54 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3

I pushed a couple of commits to avoid using a #nextPut:/#next loop in Stream>>#upToEnd. It's obviously better to just use stream-to-stream #nextPutAll:, but I had to fix a bug before. :-)

With this change #next moves a bit down in the profile on a Seaside test, and #nextPut: is also less heavily used. The latter however remains the top method in the profile, which makes sense since a web server will write much more than it reads!

It looks like the parsing of fields in Swazoo is quite expensive because of the many indirections between SwazooBuffer and SwazooStream. I'll probably look at eliminating SwazooBuffer so that operations like SwazooStream>>#upTo: and SwazooStream>>#nextUnfoldedLine can be optimized better.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]