search

namgk / ambienttalk

Automatically exported from code.google.com/p/ambienttalk
0 stars 0 forks source link

Improve performance of futures when tracing is turned off #38

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Did a small benchmark (see attached file) to measure the impact of the causeway 
tracer on 
future-type messaging. The results are poor: almost twice as slow. We need to 
improve the 
performance of future-type message passing when tracing is turned off. 
Currently, tracing info is 
attached to futures regardless of whether tracing is turned on or off.

Interactive AmbientTalk Shell, version 2.14 [build091109]
time fact(100): <java:48>
time fact(100): <java:50>
time fact(100): <java:49>
time repeat(100): <java:2550>
time repeat(100): <java:2523>
time repeat(100): <java:2539>

Interactive AmbientTalk Shell, version 2.15 (development)
time fact(100): <java:49>
time fact(100): <java:50>
time fact(100): <java:49>
>time repeat(100): <java:4473>
>time repeat(100): <java:4437>
>time repeat(100): <java:4474>

Original issue reported on code.google.com by tvcut...@gmail.com on 17 Apr 2010 at 2:58

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by tvcut...@gmail.com on 17 Apr 2010 at 2:59