Configuration Lookup is Slow

[GoogleCodeExporter]

I've been running some benchmarks of different server adapters recently. One 
thing I found out is that /files is quite slow. In fact it's about an order of 
magnitude slower than simply writing a 16 Kbyte byte array to the response.

/files has about:
150 req/sec and 500 Kbytes/sec

simply writing 16 Kbyte has about:
1500 req/sec 25000 Kbytes/sec

I simply ran:
ab -k -n 4000 http://127.0.0.1:8080/files

Surprisingly the time doesn't seem to be spent in rendering or encoding but 
WARequestHandler >> #url, more precisely looking up the four preferences. See 
the attached tally. I know /files is not a representative case of a Seaside 
page and we shouldn't optimize too hard for it but the impact of the lookup 
seems quite dramatic. If we could get it closer to a simple lookup of a Symbol 
in an IdentityDictionary that would certainly be welcomed.

Original issue reported on code.google.com by philippe...@gmail.com on 3 Nov 2010 at 6:50

Attachments:

• tally.txt