Is it possible to break your script up into a multi-threaded process? If you had a pool of 10 connections you could give each connection 150 records to process. That would make it much faster. But then you have the headache of multi-threaded process handling.
Like Brian mentioned earlier ... if it is in another database somewhere I would use something like AIE to import the data or use a DB Link if they would let me. AIE does the multi-threaded import for you automatically and runs very fast. Java API won't be much faster unless you program it like I was telling you above. It might gain you a little bit of an advantage but not much. Sean -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ravi Sent: Wednesday, July 30, 2008 12:47 PM To: [email protected] Subject: API performance question Hi: I have a application which puts data into a oracle table. A perl script takes the data from the oracle table and submits it to a single form in Remedy using ARS Perl. The application that puts the data into oracle table is a single threaded application and puts about 1500 records in 5 minutes one at a time. But the ARS perl script takes about 45 minutes to an hour. The form the script is putting the data is a single form with no filters acting on that form. Will migrating the ARS Perl code to JAVA API improve the performance? Any other suggestions. Thanks Ravi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
