Huh?

On Thu, Apr 9, 2020 at 1:09 PM Weact <we...@oblivion.io> wrote:

>
>
>
>  Is this server ready for deployment for a chat application supporting 1mm
> users or is it more in the prototype phase?
>
>
>
> We will be using group chat, roles, moderators and adding some unique chat
> threading models for distributed groups.
>
>
>
> Thanks.
>
>
>
>
>
>
>
> >
> > On Apr 9, 2020 at 11:21 AM,  <Emmanuel Lécharny (mailto:
> elecha...@gmail.com)>  wrote:
> >
> >
> >
> >  On 09/04/2020 16:01, Nitin Phuria wrote:  >  Dear Jonathan,  >   >   >
>  >  Anytime we write message to System-B session with session.write method
> the messageSent event has to be generated with it actually gets written on
> TCP/IP The messageSent event is only generated when the message has been
> fully written into the socket. A message can be written piece by piece,
> depending on the socket capacity. Also messages can be queued until the
> previous messages have been fully written. What could happen is that if you
> have a slow reader on the other side, then the socket will not be able to
> accept any data, because it gets full.  >   >   >   >
> org.apache.mina.core.session.IoSession.write(Object)  >   >   >   >  We see
> that there is time difference of 10-14 seconds between timestamp of
> session.write for particular message and messageSent event getting
> generated for the same message. So you have a problem in the middle. Check
> that the reader (ie the other server) is processing messages fast enough.
> Or maybe you have network issues, as suggests Jonathan.  >   >   >   >  In
> non-peak load this time difference is in 10-15 milliseconds and in peak
> load (60-70 messages per second) it goes till 10-14 seconds. 60/70 msg/s is
> not exceptionally high, except if you are managing big messages, or do a
> lot of processing on each message.
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: users-unsubscr...@mina.apache.org For additional
> commands, e-mail: users-h...@mina.apache.org
> >
> >
>
>
>

-- 

CONFIDENTIALITY NOTICE: The contents of this email message and any
attachments are intended solely for the addressee(s) and may contain
confidential and/or privileged information and may be legally protected
from disclosure.

Reply via email to