<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">My next project is ...<br>
      <div class="moz-cite-prefix"> <br>
        Setting up a MySQL 5.6 plus 4x MySQL Cluster NDB 7.3 in memory
        data node to increase the data <span id="result_box"
          class="short_text" lang="en"><span class="hps">throughput</span></span><br>
        <br>
        Like this one:<br>
<a class="moz-txt-link-freetext" href="http://dev.mysql.com/doc/refman/5.1/de/images/cluster-components-1.png">http://dev.mysql.com/doc/refman/5.1/de/images/cluster-components-1.png</a><br>
        <br>
        Regards<br>
        Rainer<br>
      </div>
      <br>
      <br>
      <br>
      Am 01.04.2014 09:12, schrieb Rizwan Khan:<br>
    </div>
    <blockquote
cite="mid:CALByW_EfyEErBgFg-e82RiDkR6N9ihBt=g4VBg_i1dtCdh48hA@mail.gmail.com"
      type="cite">
      <div dir="ltr">Thanks a lot Pedro.
        <div><br>
        </div>
        <div>Just one question? Do we have module for Mongodb? how do i
          use it?</div>
      </div>
      <div class="gmail_extra"><br clear="all">
        <div>Rizwan Khan<br>
          <br>
          <br>
        </div>
        <br>
        <br>
        <div class="gmail_quote">On Mon, Mar 31, 2014 at 5:52 AM, Pedro
          Niño <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:nino.pedro@gmail.com" target="_blank">nino.pedro@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <p dir="ltr">As Alex said, I/O and calls per second (CPS) is
              Dependant on what type of design you are using. </p>
            <p dir="ltr">As a tip, mysql is good for small to medium
              sizes, but begin to choke at 1000 of concurrent
              connections. but in a scalable size like you are planning,
              I would recommend to make a design with resilience and
              high availability, with mongodb or postgres as db back
              end.</p>
            <p dir="ltr">There are some good examples on internet about
              enabling multiple kamailio server with high availability
              configuration, using heartbeat and some other scripts.</p>
            <p dir="ltr">A nice design would be:</p>
            <p dir="ltr">2 or more kamailio servers, maybe virtual or
              physical, with high availability configuration (if one
              goes down, the other takes all the load)</p>
            <p dir="ltr">2 or more DB servers, also with high
              availability design.</p>
            <p dir="ltr">At least 10G connection, server and switch (for
              the call flow you're expecting) remember to make
              estimation for calls established, and codec used, (using
              g711, rtp audio might come up to 80kbps, so like 120.000
              calls is the top for a 10G connection)</p>
            <p dir="ltr">Also separate vlan for calls and server
              control, too.</p>
            <p dir="ltr">Just my 2 cents</p>
            <div class="gmail_quote">El mar 28, 2014 11:58 AM, "Rizwan
              Khan" <<a moz-do-not-send="true"
                href="mailto:rizkhan@gmail.com" target="_blank">rizkhan@gmail.com</a>>
              escribió:
              <div>
                <div class="h5"><br type="attribution">
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    <p dir="ltr">Thanks Alex. </p>
                    <p dir="ltr">What are the components that I should
                      take into account. Based on answer in another
                      thread I will be using  SIP trunk with an NGN to
                      route the outside traffic (other than SIP-SIP). </p>
                    <p dir="ltr">I'll have NATed clients so I'll need
                      the media proxy or rtp proxy as well. What about
                      their dimensioning? I am sorry if some questions
                      are really naive. I am new to all this and trying
                      to get hold of the whole technology stack. </p>
                    <p dir="ltr">Rizwan</p>
                    <div class="gmail_quote">On Mar 28, 2014 3:41 PM,
                      "Alex Balashov" <<a moz-do-not-send="true"
                        href="mailto:abalashov@evaristesys.com"
                        target="_blank">abalashov@evaristesys.com</a>>
                      wrote:<br type="attribution">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        1. Kamailio does not handle RTP, so audio is not
                        a scaling factor at all;<br>
                        <br>
                        2. The only scaling factors are transactional
                        memory (TM) and any dialog state you are
                        keeping;<br>
                        <br>
                        3. Without I/O wait from external sources,
                        Kamailio can handle a practically infinite
                        amount of concurrent calls and CPS. But, most
                        practical applications of Kamailio require
                        database backing;<br>
                        <br>
                        4. Therefore, performance and throughput will
                        depend almost entirely on the database you are
                        using for database backing, and any tuning on
                        its settings. This certainly includes the CDRs
                        and storage, and getting the most performance
                        out of your database is outside the domain of
                        your question (or this list);<br>
                        <br>
                        5. A quad-core host with 8 GB of RAM should be
                        more than sufficient for Kamailio itself to meet
                        your needs. But most of the answers to your
                        question don't have much to do with Kamailio.<br>
                        <br>
                        -- Alex<br>
                        <br>
                        On 03/28/2014 06:36 AM, Rizwan Khan wrote:<br>
                        <br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          HI Guys,<br>
                          <br>
                          can you refer me to some resources which help
                          me dimension the hardware<br>
                          for a setup.<br>
                          <br>
                          Total users will be 20,000. What percentage
                          should i assume for<br>
                          concurrent audio and video calls? What is the
                          standard practice? How<br>
                          does this all map to the cpu, ram and storage
                          etc. given that I will be<br>
                          storing the cdrs as well.<br>
                          <br>
                          In the futute this setup should be scalable so
                          that it should support<br>
                          200,000+ users within a span of 6-8 months.
                          What would be the ideal<br>
                          architecture?<br>
                          <br>
                          Thanks,<br>
                          <br>
                          Rizwan Khan<br>
                          <br>
                          <br>
                          <br>
                          <br>
                          _______________________________________________<br>
                          SIP Express Router (SER) and Kamailio
                          (OpenSER) - sr-users mailing list<br>
                          <a moz-do-not-send="true"
                            href="mailto:sr-users@lists.sip-router.org"
                            target="_blank">sr-users@lists.sip-router.org</a><br>
                          <a moz-do-not-send="true"
                            href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
                            target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
                          <br>
                        </blockquote>
                        <br>
                        <br>
                        -- <br>
                        Alex Balashov - Principal<br>
                        Evariste Systems LLC<br>
                        235 E Ponce de Leon Ave<br>
                        Suite 106<br>
                        Decatur, GA 30030<br>
                        United States<br>
                        Tel: <a moz-do-not-send="true"
                          href="tel:%2B1-678-954-0670"
                          value="+16789540670" target="_blank">+1-678-954-0670</a><br>
                        Web: <a moz-do-not-send="true"
                          href="http://www.evaristesys.com/"
                          target="_blank">http://www.evaristesys.com/</a>,
                        <a moz-do-not-send="true"
                          href="http://www.alexbalashov.com/"
                          target="_blank">http://www.alexbalashov.com/</a><br>
                        <br>
                        _______________________________________________<br>
                        SIP Express Router (SER) and Kamailio (OpenSER)
                        - sr-users mailing list<br>
                        <a moz-do-not-send="true"
                          href="mailto:sr-users@lists.sip-router.org"
                          target="_blank">sr-users@lists.sip-router.org</a><br>
                        <a moz-do-not-send="true"
                          href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
                          target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
                      </blockquote>
                    </div>
                    <br>
                    _______________________________________________<br>
                    SIP Express Router (SER) and Kamailio (OpenSER) -
                    sr-users mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:sr-users@lists.sip-router.org"
                      target="_blank">sr-users@lists.sip-router.org</a><br>
                    <a moz-do-not-send="true"
                      href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
                      target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
                    <br>
                  </blockquote>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
            mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
            <a moz-do-not-send="true"
              href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
              target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <b>Rainer Piper</b>
      <br>
      NOC - +49 (0)228 97167161 - sip.soho-piper.de
      <br>
      NOC - +49 (0)2247 9064188 - sip.tele33.de - sip.tefonix.de - D293
    </div>
  </body>
</html>