Paul Johnston wrote:
> Just out of interest, is there anything specific (pitfalls, known
> issues) that I should be aware of when load testing applications built
> on cgiapp?
C::A is extremely lightweight (lighter than any other framework that I'm aware
of) so I doubt the problem is there. But, there are some things tangentially
related to most C::A projects that might help...
+ what templating engine are you using? TT and H::T have decent cache systems
that can be tweaked to give you better performance, although in reality your
templating isn't your bottleneck
+ are you running under mod_perl/FastCGI? They can help significantly to avoid
loading time hits and C::A is next to perfect for use under both of those.
> I've just built what I think is a decent cgiapp (clean, small etc) and
> have found that it's sluggish when under load. I've optimised the
> database connections and checked logs etc, but can't seem to find the
> issue. I'm thinking it may be my apache setup, but I thought there
> might be a few obvious things specific to cgiapp that I could check.
How did you optimize your db connections?
> Any obvious optimisations for cgiapp? Any obvious places I should check?
>
> Most likely thing is a coding error (obviously) somewhere within the app.
You could look at C::A::Plugin::DevPopup and some of the other plugins that can
run under it (C::A::P::DevPopup::Timing)
But the advice about using dbprof is probably the best.
--
Michael Peters
Developer
Plus Three, LP
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.