Hi,
> Np. This was a good exercise, and I'm happy that somehow, these mails
allowed you to get the confirmation that you didn't do anything wrong
with MINA.
It's the first time we use a library for protocol implementation based upon
the reactor pattern.
Actually after getting used to how it is
Le 2/25/14 9:34 AM, Max Larsson a écrit :
> Hi,
>
> i think i found the problem. The problem is the guy writing this
> eMail :-)
>
> Actually everything is completely right, my mind just wanted to have
> a different output via the log messages.
>
> Explanation:
>
> In the first test run, we didn't
Hi,
i think i found the problem. The problem is the guy writing this
eMail :-)
Actually everything is completely right, my mind just wanted to have
a different output via the log messages.
Explanation:
In the first test run, we didn't reach the aimed goal, because the
complete cycle took about
Le 2/24/14 8:06 AM, Max Larsson a écrit :
> Hi,
>>> Upon receiving Started, our app has to to respond with a new
>>> set of data to print. The processing of this takes about ~2ms.
>>> (NioPreccossor recievedMessage -> session.write).
>>
>> you mean it takes 2ms to process a message on your server ?
Hi,
>> The stress test was made with two different setup one being a MacBookPro
2011 with our software running under Mac OS 19.1. And a windows laptop
with a virtual machine running a linux application, doing the same task,
as our implementation. (Our application shall replace the linux one).
An
Le 2/23/14 2:52 PM, Max Larsson a écrit :
> Hi,
>
> >> The logs i based my investigation on are from a a stress test. And
>>> the external measurement has the same result.
>>>
>>> Actually the timing from receiving,proceesing,session.write the
>>> commands
>>> is very constant on my side (~2ms). Th
Hi,
>> The logs i based my investigation on are from a a stress test. And
the external measurement has the same result.
Actually the timing from receiving,proceesing,session.write the commands
is very constant on my side (~2ms). The time between session.write and
messageSent event is normally a
Le 2/22/14 5:06 PM, Max Larsson a écrit :
> Hi,
>
> The logs i based my investigation on are from a a stress test. And
> the external measurement has the same result.
>
> Actually the timing from receiving,proceesing,session.write the commands
> is very constant on my side (~2ms). The time between
Hi,
The logs i based my investigation on are from a a stress test. And
the external measurement has the same result.
Actually the timing from receiving,proceesing,session.write the commands
is very constant on my side (~2ms). The time between session.write and
messageSent event is normally about
Instead of relying on logging; I would setup a stress test to measure
completed commands/s and use that as a foundation for trying other
procedures.
On Sat, Feb 22, 2014 at 7:03 AM, Max Larsson
wrote:
> Hi,
>
> >>
> >>
>
>> In my IoHandler i receive the desired message and write out the res
Hi,
>>
>>
In my IoHandler i receive the desired message and write out the response
to session.write. But it is not immediately written out. During my
process of the message additional message are received and process
before my response message is delivered.
It all depends on the session p
Le 2/21/14 6:10 PM, Max Larsson a écrit :
> Hi,
>
> i've got a very asynchronous protocol to implement. Where if have to
> respond as fast as possible to retrieve message.
>
> In my IoHandler i receive the desired message and write out the response
> to session.write. But it is not immediately writ
Hi,
i've got a very asynchronous protocol to implement. Where if have to
respond as fast as possible to retrieve message.
In my IoHandler i receive the desired message and write out the response
to session.write. But it is not immediately written out. During my
process of the message additional
13 matches
Mail list logo
