D'oh. *And* he knows I was silly enough to set all my usernames and
passwords to "xxx". Wait - now *everyone* knows!
Jaime
> -Original Message-
> From: Brad Wood [mailto:b...@bradwood.com]
> Sent: Thursday, 5 February 2009 3:33 PM
> To: cf-talk
> S
Oh man, you fell for it. Now Jochem has all your datasource passwords. :)
His plan for total world annihilation is one step closer now...
~Brad
- Original Message -
From: "Jaime Metcher"
>
> Sent to you off-list. Thanks for having a look.
>
> Jaime
>> Could you grab the full sett
Jochem,
Sent to you off-list. Thanks for having a look.
Jaime
> -Original Message-
> From: Jochem van Dieten [mailto:joch...@gmail.com]
> Sent: Wednesday, 4 February 2009 10:19 PM
> To: cf-talk
> Subject: Re: Connection pooling - why bother?
>
>
> On Tue,
On Tue, Feb 3, 2009 at 11:46 PM, Jaime Metcher wrote:
> And for the CF datasource:
> class="coldfusion.server.ServiceFactory"
> factory-method="getDataSourceService"/>
> factory-method="getDatasource">
>
>
>
> And then I go into the CF admin and turn "mainta
k that).
Jaime
> -Original Message-
> From: Jochem van Dieten [mailto:joch...@gmail.com]
> Sent: Wednesday, 4 February 2009 5:00 AM
> To: cf-talk
> Subject: Re: Connection pooling - why bother?
>
>
> On Fri, Jan 30, 2009 at 10:12 AM, Jaime Metcher wrote:
>
On Fri, Jan 30, 2009 at 10:12 AM, Jaime Metcher wrote:
> Just wondering if anyone has benchmarked CF's connection pooling. I'm
> getting results suggesting that turning on "maintain connections" does
> basically nothing for performance, and that using an alternative unpooled
> connection provider
Not using connection pooling, in our environment, significantly slow
down all process, and increases overhead to an order that eventually
will bring a server to a complete non-responsive state. Basically, you
end up tying up every available active thread request with long running
DB requests,
It certainly isn't for us. Connection pooling always gives us quicker
queries; this is even more true now that we use dedicated servers, but
it was true back when we used shared servers too (we're on Oracle).
mxAjax / CFAjax docs and other useful articles:
http://www.bifrost.com.au/blog/
2009/
Hey Cutter,
> in our environment we would be insane not to use connection pooling.
...unless it's actually faster to not use connection pooling. So is it?
Jaime
~|
Adobe® ColdFusion® 8 software 8 is the most important and d
Good points.
It seems to be an ORACLE thing. You can make the Global Temporary table
either transaction or session specific using the ON COMMIT clause (DELETE
ROWS or PRESERVE ROWS). No, we don't drop tables since there is only one
type of temporary table. You just specify how it responds t
drop them after usage if for no other reason than to not
have them laying around later if a connection is reused?
~Brad
- Original Message -
From: "Craigsell"
To: "cf-talk"
Sent: Friday, January 30, 2009 10:16 PM
Subject: Re: Connection pooling - why bother?
>
There is one other thing to consider in using connection pooling. I admit
it is a bit off the beaten path but it bit me pretty good. I use Oracle
stored procedures as much as I can. You cannot use connection pooling if
your stored proc uses Global Temporary Tables. Since the connection is
m
I guess it depends on your application, and the traffic you expect. One
of our servers will process 500k db requests in a 4 hour period
(according to FusionReactor), so in our environment we would be insane
not to use connection pooling.
Steve "Cutter" Blades
Adobe Certified Professional
Advanced
13 matches
Mail list logo
