Re: performance problem with oracle dbd

Take a look at your inserts, are you using auto commits? if so every insert is casuing a commit, are you executing the same sql as the sqlplus is executing? Are the DBD settings similar to sqlplus's settings for buffer size and maximum window? Are you using placeholders?

-Waswas

Comment on Re: performance problem with oracle dbd

Replies are listed 'Best First'.
Re: Re: performance problem with oracle dbd by tito (Novice) on Apr 15, 2004 at 17:42 UTC
Thanks for the reply, The performance problem is worse with the actual app. The five times performance slow down was verified by running two stripped down tests with identical insert statements and commit frequencies. One test was coded using PL/SQL looping construct and the other using perl. I will go and take a look at the documentation and see how one can set the buffer and windows sizes for DBD since I've not set those parameters for DBD.	[reply]
Re: Re: Re: performance problem with oracle dbd by perrin (Chancellor) on Apr 15, 2004 at 19:47 UTC
The PL/SQL code doesn't have any network overhead, so naturally it will be faster. PL/SQL is not a general-purpose language, so it can't do the same things Perl can, but if it meets your needs and speed is extremely important for this project, I'd say use it.	[reply]
Re: performance problem with oracle dbd by Roy Johnson (Monsignor) on Apr 15, 2004 at 18:23 UTC
PL/SQL is faster than DBD because it's all executed on the database side, rather than using multiple transactions. There is nothing wrong with throwing a chunk of PL/SQL into your Perl, if that's appropriate for what you want to do. It works fine. The PerlMonk `tr///` Advocate	[reply]


more useful options
	PerlMonks