depending on what you need. I've always been happy with httpload, which is
an incredibly simple app (for *nix at least, don't know about windows) that
will take a set of URLs, and request them at whatever speed you want, for
however long you want, and then generate a nice little report afterwards.
It's far from feature rich, but it's a very effective tool.
<rant>
"is cfloop really needed" is a horrible thing to look at before you do load
testing. Improperly indexed databases, and ineffecient queries are the
major culprits, so until you've exhaustively tested those, worry about
nothing else. Once that's done, look for caching opportunities on the front
side of the application (cache pregenerated content, either in memory, or as
static files). Once that's done, make sure you code is as readable and well
encapsulated as possible. After that, think about increasing the hardware
resources that drive the application (split app and DB between boxes, make a
cluster, add more servers to the cluster, whatever). Next, go BBQ some
steaks, have a few beers, and watch some TV. Then start rewriting the
application in a language designed with performance closer to the top of the
priority list than CF (JSP would be a start, pure Servlets is better, some
C/C++ web server filters/modules, and then perhaps even a dedicated
webserver/application combination). Time to check the hardware setup again.
Almost done now. Time for another BBQ, this time with some nice bratwurst,
and maybe some fresh grilled corn on the cob. Finally, think about removing
loops that aren't strictly necessary, but make code more readable.
And of course, don't forget to load test after each and every step,
excluding the BBQ ones.
</rant>
Cheers,
barneyb
> -----Original Message-----
> From: Yves Arsenault [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 18, 2004 4:52 PM
> To: CF-Talk
> Subject: Load testing
>
>
> Hello,
>
> I was wondering what was the general pratice for testing your
> app is....
>
> Is there any way of similating a certain number of hits per minute?
>
> I'd like to test some sections of some apps and see what kind
> of performance
> my code is getting (or not getting).
>
> Does anyone have any suggestions as to how this test could be done?
>
>
> There are some projects that are coming up that I would
> really love to use
> some kind of checking to really tighten up performance as
> much as possible.
> I liked the example on the houseoffusion.com home page where
> the question
> was asked, "Is CFLOOP really needed?"... little tricks like
> that, I'm sure
> are almost trivial but running sloppy queries/loops....etc...
> Just want to
> tighten it up.
>
> Any ideas?
>
> Thanks,
>
> Yves Arsenault
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
