Optimizing bulk xml data insert in postgresql 9.6












1















I am currently optimizing an xml parser where I currently have a bottleneck on a bulk insert of 10,000 records into an xml array in postgres. This version of postgres does not implement xmltable. The following code is what I currently have:



create unlogged table xmltable(
xml_element1 xml,
xml_element2 xml,
xml_element3 xml
);

v_xml := XMLPARSE(DOCUMENT convert_from(src_blob, 'UTF8') );

INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
SELECT
(xpath ('element1parent/element1feature', x_xml)),
(xpath ('element2parent/element2feature', x_xml)),
(xpath ('element3parent/element3feature', x_xml)),
FROM (SELECT unnest(xpath('/Root/grandparent',v_xml)) as x_xml);

drop table xmltable;


Current processing time is about 4 minutes for xml_element1 = 40 inserts,
xml_element2 = 9,980 inserts, xml_element3 = 0 inserts.


A couple things I've tried are:



Switch between temporary and unlogged table
Breaking up query
using v_xml := convert_from(src_blob, 'UTF8')::xml



Any insight would be greatly appreciated!










share|improve this question



























    1















    I am currently optimizing an xml parser where I currently have a bottleneck on a bulk insert of 10,000 records into an xml array in postgres. This version of postgres does not implement xmltable. The following code is what I currently have:



    create unlogged table xmltable(
    xml_element1 xml,
    xml_element2 xml,
    xml_element3 xml
    );

    v_xml := XMLPARSE(DOCUMENT convert_from(src_blob, 'UTF8') );

    INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
    SELECT
    (xpath ('element1parent/element1feature', x_xml)),
    (xpath ('element2parent/element2feature', x_xml)),
    (xpath ('element3parent/element3feature', x_xml)),
    FROM (SELECT unnest(xpath('/Root/grandparent',v_xml)) as x_xml);

    drop table xmltable;


    Current processing time is about 4 minutes for xml_element1 = 40 inserts,
    xml_element2 = 9,980 inserts, xml_element3 = 0 inserts.


    A couple things I've tried are:



    Switch between temporary and unlogged table
    Breaking up query
    using v_xml := convert_from(src_blob, 'UTF8')::xml



    Any insight would be greatly appreciated!










    share|improve this question

























      1












      1








      1








      I am currently optimizing an xml parser where I currently have a bottleneck on a bulk insert of 10,000 records into an xml array in postgres. This version of postgres does not implement xmltable. The following code is what I currently have:



      create unlogged table xmltable(
      xml_element1 xml,
      xml_element2 xml,
      xml_element3 xml
      );

      v_xml := XMLPARSE(DOCUMENT convert_from(src_blob, 'UTF8') );

      INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
      SELECT
      (xpath ('element1parent/element1feature', x_xml)),
      (xpath ('element2parent/element2feature', x_xml)),
      (xpath ('element3parent/element3feature', x_xml)),
      FROM (SELECT unnest(xpath('/Root/grandparent',v_xml)) as x_xml);

      drop table xmltable;


      Current processing time is about 4 minutes for xml_element1 = 40 inserts,
      xml_element2 = 9,980 inserts, xml_element3 = 0 inserts.


      A couple things I've tried are:



      Switch between temporary and unlogged table
      Breaking up query
      using v_xml := convert_from(src_blob, 'UTF8')::xml



      Any insight would be greatly appreciated!










      share|improve this question














      I am currently optimizing an xml parser where I currently have a bottleneck on a bulk insert of 10,000 records into an xml array in postgres. This version of postgres does not implement xmltable. The following code is what I currently have:



      create unlogged table xmltable(
      xml_element1 xml,
      xml_element2 xml,
      xml_element3 xml
      );

      v_xml := XMLPARSE(DOCUMENT convert_from(src_blob, 'UTF8') );

      INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
      SELECT
      (xpath ('element1parent/element1feature', x_xml)),
      (xpath ('element2parent/element2feature', x_xml)),
      (xpath ('element3parent/element3feature', x_xml)),
      FROM (SELECT unnest(xpath('/Root/grandparent',v_xml)) as x_xml);

      drop table xmltable;


      Current processing time is about 4 minutes for xml_element1 = 40 inserts,
      xml_element2 = 9,980 inserts, xml_element3 = 0 inserts.


      A couple things I've tried are:



      Switch between temporary and unlogged table
      Breaking up query
      using v_xml := convert_from(src_blob, 'UTF8')::xml



      Any insight would be greatly appreciated!







      xml postgresql xpath query-optimization






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 18:02









      user10659111user10659111

      61




      61
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I figured it out, the unnest function is unescessary and accumulates alot of overhead.



          This was way faster:



          INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
          SELECT
          (xpath ('/Root/grandparent/element1parent/element1feature', v_xml)),
          (xpath ('/Root/grandparent/element2parent/element2feature', v_xml)),
          (xpath ('/Root/grandparent/element3parent/element3feature', v_xml));





          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325420%2foptimizing-bulk-xml-data-insert-in-postgresql-9-6%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I figured it out, the unnest function is unescessary and accumulates alot of overhead.



            This was way faster:



            INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
            SELECT
            (xpath ('/Root/grandparent/element1parent/element1feature', v_xml)),
            (xpath ('/Root/grandparent/element2parent/element2feature', v_xml)),
            (xpath ('/Root/grandparent/element3parent/element3feature', v_xml));





            share|improve this answer




























              0














              I figured it out, the unnest function is unescessary and accumulates alot of overhead.



              This was way faster:



              INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
              SELECT
              (xpath ('/Root/grandparent/element1parent/element1feature', v_xml)),
              (xpath ('/Root/grandparent/element2parent/element2feature', v_xml)),
              (xpath ('/Root/grandparent/element3parent/element3feature', v_xml));





              share|improve this answer


























                0












                0








                0







                I figured it out, the unnest function is unescessary and accumulates alot of overhead.



                This was way faster:



                INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
                SELECT
                (xpath ('/Root/grandparent/element1parent/element1feature', v_xml)),
                (xpath ('/Root/grandparent/element2parent/element2feature', v_xml)),
                (xpath ('/Root/grandparent/element3parent/element3feature', v_xml));





                share|improve this answer













                I figured it out, the unnest function is unescessary and accumulates alot of overhead.



                This was way faster:



                INSERT INTO xmltable ( xml_element1, xml_element2, xml_element3)
                SELECT
                (xpath ('/Root/grandparent/element1parent/element1feature', v_xml)),
                (xpath ('/Root/grandparent/element2parent/element2feature', v_xml)),
                (xpath ('/Root/grandparent/element3parent/element3feature', v_xml));






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 15 '18 at 20:39









                user10659111user10659111

                61




                61
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325420%2foptimizing-bulk-xml-data-insert-in-postgresql-9-6%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Bressuire

                    Vorschmack

                    Quarantine