Re: [boost] [async] messages threads and networks

Subject: Re: [boost] [async] messages threads and networks
From: Scott Woods (scott_at_[hidden])
Date: 2010-04-25 03:55:25

>> This basically looks appealing. I have one question though. I jumped 
>> through
>> a few hoops so that registration does not need to mention the type - it 
>> is
>> auto-generated from the member name. I would be happy to leverage the 
>> work
>> of Fusion but sad to lose the correctness guarantee offered by
>> auto-generating
>> the type. Can Fusion offer that as well?
>>
>> As the types get more complicated the chances of a registration error 
>> (i.e.
>> an
>> incorrectly associated type ) move from "possible" to "expected".
>
> Fusion is completely compile-time in how it can assign 'views' to
> types, but your type registration is independent, hence why making
> your own macro that handle that and the fusion view adaptation would
> be best, it would negate the need for your operator>>/<< functions is
> all it is, would vastly simplify code and reduce chance of errors.

Yes, I can see real benefit. Always preferred to have Boost but
didnt want to impose prerequisite on potential users. Perhaps I
was wrong.

>> More speed? Always interested in making software faster but where is
>> it slow?
>>
>> I also enjoy code examples but have you downloaded the samples
>> solution yet? You are asking for more code beyond that provided in the
>> samples?
>
> I was not asking if it was slow, just asking if you had speed reports
> and comparisons, through-put tests for network (perhaps in comparison
> to other libs, Raknet for example, or Erlang too for massage passing
> tests?), etc...

Ah yes. I spent substantial time on performance testing. Would love to
carry out comparison testing. Time and technical resources are the only
limiting factors.

If you are truly interested in statistics I can send some results to you
directly. Reviewing the numbers was both interesting and confusing.
One informal performance metric is the number of times a message can
be sent between two points;

* same thread, same process = 220k/second
* different threads, same process = 120k/second
* different threads, different process, same PC = 11k/second
* different threads, different process, different PC = 1100/second (54Mb 
wireless)

>
> Cannot try to compile it right now, my main computer is down, and
> Visual Studio does not work on PocketPC/Arm.

Time for an iPhone? OK it doesn't run there either but just having
one would make you feel better.

Cheers,
Scott