To be fair, performance of an ASPX web site can be killed by bad programming as well as running a site natively.
At least 90% of the performance issues arise from bad database access design or lack of proper indexing and record selection on any platform.
Even if the system spawns a lot of QZDSAOINIT jobs they are usually running at 0% unless you are doing some large table scans of interesting joins :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 3
date: Tue, 12 Apr 2011 07:35:31 -0400
from: Brian Piotrowski <bpiotrowski@xxxxxxxxxxxxxxx>
subject: Re: [WEB400] iSeries vs IIS web site
Not sure of any sites, but you should know that if you are using the iSeries to host the data that feeds your IIS server that it takes a HUGE amount of overhead (in the area of 40% of cpu utilization in some instances!) when serving this data. If you are so inclined, and you do this, check out how many QZDASOINIT jobs you have and how much cpu overhead it takes up.
We are in the middle of moving all of our web sites back to our 400. We hired a programmer who is ASPX/PHP savvy and he will be converting all of our ASP/ASPX code to PHP.
/b;
midrange.com
