From: Alex B. <en...@tu...> - 2001-07-11 18:54:36
|
> I have to agree with alex on this. > I've been working with 2 different systems. > One, running NAS(netscape application server) 4.0, > with all the servlets/EJB/JSP architecture > mumbo-jumbo. > And the other, running PHP4. > > It turns out that the NAS, having only served > 20-customer have a CPU utilization of nearly 80% > while the system running PHP4, only utilize about 25% > of the CPU. :) > And FYI, the NAS is hosted on a E10K server with a > spec beyond this realm of existence, while the PHP > system is hosted on a humble DELL Pentium III PC with > only 256Mb Ram with a single CPU. :) I love php :) > Both system run more or less the same application. > It turns out that for the NAS system, we have to incur > additional cost to hire the so-called "NAS specialist" > to identify the bottleneck and "optimize" further the > system...puhhlleaassee...still they only managed to heh. > I can do way much better using PHP. The only good > thing about using NAS is that you can have somebody > else to blame for the crappy performance. Yes! I was involved with a project using jrun a while ago, not only was it buggy (lots of padding at the top and bottom of every file, or it would crash, no double-byte chars, etc etc) it was a pain in the a** to work with. Of everything I've worked with, php is both the fastest and most efficient. of course, because it doesn't force any structure, it's easy to write spaghetti if you're not thinking about it. (problem solved :) _a -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |