What's the CPU load like when the reporting page is being accessed? I
have something similar in one of my projects and had to introduce
caching for the reporting pages due to the way it would hammer the CPU
(99% usage for upwards of 10 minutes). Luckily I have the application
running on a dual processor machine, so the second processor would be
available to handle further incoming requests.
I'm still running Webware 0.8.1 myself and have found the only
limitation to handling simultaneous and long running requests is CPU
Hope this helps,
Leigh Dyer wrote:
> I've been using WebWare in a low-volume production environment for a
> while now, but as the load has increased I've started to notice some
> crack forming. Specifically, one issues that causes trouble is that
> when someone accesses a reporting page on one site, which can take a
> minute or two to run, other sites seem to be largely unaccessible
> until the original request is complete.
> Is this a known issue, or something odd with my particular setup? --
> I'm assuming the latter for now, given the lack of similar complaints.
> The server in question is running WebWare 0.8.1 under Apache 2.0
> (using the mod_webkit2 connector) on Debian Sarge, using Python 2.3.
> The apps are connecting to a SQL Server database using the Object
> Craft Sybase module. If there's any other info I can provide please
> let me know.
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> that extends applications into web and mobile media. Attend the live
> and join the prime developer group breaking into this new coding
> Webware-discuss mailing list