Thanks for the reply. DML also implies query parsing, mapping to Java objects and other > preparation steps before IgniteDataStreamer API is called. Thus the > performance difference.
Does this mean the data streamer api would be faster in pre-loading or bulk-data as compared to the streaming mode jdbc driver? Thanks. On Wed, Mar 15, 2017 at 12:24 AM, vkulichenko [via Apache Ignite Users] < [email protected]> wrote: > 1. Yes, it's using IgniteDataStreamer under the hood and even has the same > parameters. > 2. DML also implies query parsing, mapping to Java objects and other > preparation steps before IgniteDataStreamer API is called. Thus the > performance difference. > > -Val > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Understanding-faster-batch- > inserts-updates-with-apache-ignite-1-9-tp11117p11170.html > To unsubscribe from Understanding faster batch inserts/updates with apache > ignite 1.9, click here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11117&code=YW1pdHMuODRAZ21haWwuY29tfDExMTE3fDU1OTcxMzI3Nw==> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Understanding-faster-batch-inserts-updates-with-apache-ignite-1-9-tp11117p11195.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
