<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>Hi Alex,<br>
      <br>
      Typical approach in this case is to do the accounting via a very
      fast backend (like db_flatstore, into a text file) and import the
      files off-sync into db (like every 5 mins).<br>
      <br>
      Regards,<br>
    </tt>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>

</pre>
    <div class="moz-cite-prefix">On 4/23/20 4:37 PM, Alex A wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:171a7422dea.1247b83848131.3910812018483636749@gtanetworkconsulting.com">
      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
      <div style="font-family: Verdana, Arial, Helvetica, sans-serif;
        font-size: 10pt;">
        <div data-zbluepencil-ignore="true" style="" class="zmail_extra">
          <div>
            <div style="font-family: Verdana, Arial, Helvetica,
              sans-serif;font-size: 10.0pt;">
              <div>Hi,<br>
              </div>
            </div>
          </div>
          <blockquote style="border-left: 1px solid rgb(204, 204, 204);
            padding-left: 6px; margin: 0px 0px 0px 5px;">
            <div>
              <div style="font-family: Verdana, Arial, Helvetica,
                sans-serif;font-size: 10.0pt;">
                <div><br>
                </div>
                <div>We are looking to deploy accounting/homer
                  integration on Opensips 3.0.2. <br>
                </div>
                <div>As the first step deployed acc module with pgsql
                  backend. <br>
                </div>
                <div><br>
                </div>
                <div>The config seem to be pretty straight-forward - see
                  attached. <br>
                </div>
                <div><br>
                </div>
                <div>It appears that as soon as volume hits about 30-35k
                  in_use transactions - the server stops replying to new
                  requests (or give 408 Timeout) and syslog gets filled
                  with:<br>
                </div>
                <div><br>
                </div>
                <div>Apr 22 10:19:38 opensip1 opensips: Apr 22 10:19:38
                  [19258] CRITICAL:tm:set_timer: set_timer for 1 list
                  called on a "detached" timer -- ignoring:
                  0x7fb63b993cf8<br>
                </div>
                <div>Apr 22 10:19:40 opensip1 opensips: Apr 22 10:19:40
                  [19255] CRITICAL:tm:set_timer: set_timer for 1 list
                  called on a "detached" timer -- ignoring:
                  0x7fb638cf9a40<br>
                </div>
                <div>Apr 22 10:19:40 opensip1 opensips: Apr 22 10:19:40
                  [19260] CRITICAL:tm:set_timer: set_timer for 1 list
                  called on a "detached" timer -- ignoring:
                  0x7fb63f3b23c8<br>
                </div>
                <div>Apr 22 10:19:49 opensip1 opensips: Apr 22 10:19:49
                  [19258] CRITICAL:tm:set_timer: set_timer for 1 list
                  called on a "detached" timer -- ignoring:
                  0x7fb63eb93a80<br>
                </div>
                <div>Apr 22 10:20:01 opensip1 opensips: Apr 22 10:20:01
                  [19267] CRITICAL:tm:set_timer: set_timer for 1 list
                  called on a "detached" timer -- ignoring:
                  0x7fb5de690700<br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Although, the remote Postgres service is on SSD
                  with relatively small network latency, it appears to
                  be the bottleneck.<br>
                </div>
                <div>The initial assumption was the Opensips acc uses
                  no-blocking SQL calls (since cdrs are not real-time).<br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Another observation: <br>
                </div>
                <div>opensips only opens 20 SQL connections to postgres
                  via tcp 5432.  I have tried playing with
                  db_max_async_connections, however to no avail. <br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Any suggestions to troubleshoot ? or any
                  alternatives for accounting in high volume
                  applications would be greatly appreciated. <br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Thank you.<br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
              </div>
              <br>
            </div>
          </blockquote>
        </div>
        <div><br>
        </div>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>