<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Background processing Vs Parallel processing in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121292#M1904727</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naveen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also faced same kind of issue and resolved using 1st option by creating a wrapper program to call original program and collecting errors in application log and error table for reprocessing the error records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. If records are independent on each other and you don't need to show the output then you can go by scheduling multiple background jobs based on volume of records per job. In this case, if you want to track&amp;nbsp; list of errors and other information by creating a application log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;2. if you are collecting the data from database and then for processing of your logic if it takes larger time then you can create a function module for you processing or calculation and execute in some other destination. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Get all the results and maintain some temp db table and update using that table by using proper locking mechanism.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;SaiKrishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Jun 2015 17:36:20 GMT</pubDate>
    <dc:creator>sai_krishna24</dc:creator>
    <dc:date>2015-06-10T17:36:20Z</dc:date>
    <item>
      <title>Background processing Vs Parallel processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121289#M1904724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;I need to process 10 lakh entries in a program which takes lot of time may be days together.So thinking of splitting the records into smaller size and then processing it, like dividing the 10 lakh records into may be 2 lakh records within the program and process them parallely.Is it going to be good to process parallely in the program using "Parallel processing" concept or creating 5 background job within the program and make them run in the background? Need advice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With thanks &amp;amp; regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2015 16:10:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121289#M1904724</guid>
      <dc:creator>former_member282968</dc:creator>
      <dc:date>2015-06-10T16:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: Background processing Vs Parallel processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121290#M1904725</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think multiple background job of same program will be easiest &amp;amp; quicker way , but you need to consider about database locks .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Raj Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2015 16:44:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121290#M1904725</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-06-10T16:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: Background processing Vs Parallel processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121291#M1904726</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Naveen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It depends on your requirement. Do you want the results back from the processing to write an output or calculate something? If yes, you cannot use background processing and you need to run parallel threads in which you have an option to get the results back from the function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vikram.M&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2015 17:11:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121291#M1904726</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-06-10T17:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: Background processing Vs Parallel processing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121292#M1904727</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naveen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also faced same kind of issue and resolved using 1st option by creating a wrapper program to call original program and collecting errors in application log and error table for reprocessing the error records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. If records are independent on each other and you don't need to show the output then you can go by scheduling multiple background jobs based on volume of records per job. In this case, if you want to track&amp;nbsp; list of errors and other information by creating a application log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;2. if you are collecting the data from database and then for processing of your logic if it takes larger time then you can create a function module for you processing or calculation and execute in some other destination. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Get all the results and maintain some temp db table and update using that table by using proper locking mechanism.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;SaiKrishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2015 17:36:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-processing-vs-parallel-processing/m-p/11121292#M1904727</guid>
      <dc:creator>sai_krishna24</dc:creator>
      <dc:date>2015-06-10T17:36:20Z</dc:date>
    </item>
  </channel>
</rss>

