The database was sql server. From what I've read so far I agree that those
are the default settings. I don't know exactly why the speed improved. The
profiled timings of the calls even with the same connection string do have
some significant variation. There is more work to do, but after 4 tries e
On Thu, August 6, 2009 11:21 pm, Jonathan Lim said:
>
> Michael,
>
> Thank you for your quick reply. A quick test of adding
>
> Max Pool Size=100;Pooling=true
>
> to the connection string did improve the performance of the open
> connection
> routine enough that it is no longer the slowest routine
Awesome, glad to see it worked
On Thu, Aug 6, 2009 at 2:21 PM, Jonathan Lim wrote:
>
> Michael,
>
> Thank you for your quick reply. A quick test of adding
>
> Max Pool Size=100;Pooling=true
>
> to the connection string did improve the performance of the open connection
> routine enough that it i
Michael,
Thank you for your quick reply. A quick test of adding
Max Pool Size=100;Pooling=true
to the connection string did improve the performance of the open connection
routine enough that it is no longer the slowest routine.
Thanks again for the direction to go towards,
Jonathan
Michael M
Couple of things.
What database are you backing this against? Do you have connection pooling
enabled?
On Thu, Aug 6, 2009 at 12:34 PM, Jonathan Lim wrote:
>
> Hi,
>
> I'm a relative iBatis novice. The guy who knew much about iBatis left the
> company about 3 years ago.
>
> We have iBatis.Net
5 matches
Mail list logo
