This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: [Slashcode] PHPSlash vs Slash..
From: Chris Nandor <chris.nandor@andover.net>
Date: Mon, 28 Feb 2000 14:34:26 -0500
At 14.16 -0500 2000.02.28, Chad Day wrote:
>I was under the impression that PHP was faster/more efficent than perl. I'm
>not sure if it's to the point where it actually -matters-, but it's always
>nice. :)
Some people try to convince me PHP is a lot faster, but I don't believe it.
What I do believe is that mod_perl takes up a lot more memory than PHP
does, and that this can cause your system to be a lot slower if you are
short on RAM. It is the major drawback of mod_perl (and one of the
drawbacks of Perl itself), that you sacrifice speed and ease and features
and cool stuff for RAM. I don't happen to mind that, but some people do.
Some people dislike Perl itself because of how the language works, and so
the extra RAM it takes up isn't justifiable to them.
===
Subject: Re: [Slashcode] PHPSlash vs Slash..
From: "James Turinsky" <turinsky@somesites.com>
Date: Mon, 28 Feb 2000 14:53:57 -0500
[cc: phpslash@lists.netuse.de for them to debunk anything]
Chris Nandor <chris.nandor@andover.net> wrote:
>At 13.44 -0500 2000.02.28, Chad Day wrote:
>>My experiences, having setup and ran a PHPSlash site (www.e-league.com)..
[snippage]
>>PHPSlash is faster.
>
>I don't buy it. Slash is basically instantaneous in my machines. YMMV, I
>suppose.
Well, exactly *what* kind of machines are you using? SMP PIII's?
Overclocked Athlons? You got 512MB RAM in those suckers?
I'll buy it on the grounds that mod_perl tends to suck a lot of RAM and on
older machines (say a P-200 no MMX with the maximum 128MB EDO DRAM) you can
start running outta RAM and into swap with good amounts of traffic.
[top output]
With mod_perl only:
27074 nobody 1 0 5816 5816 5604 S 0 0.0 4.5 0:00 httpd
With mod_perl and mod_php3:
27088 nobody 1 0 6300 6300 6092 S 0 0.0 4.9 0:00 httpd
Also PHP can be made --with-mysql which I believe ties in MySQL bits and
pieces, as compared to calling other bits of Perl to talk to MySQL. PHP
effectively becomes a MySQL client inside of Apache or something.
Someone will correct me, I'm sure...
>>If PHPSlash supported user login, I would switch in a heartbeat.. due to
PHP's
>>speed, ease of use, ease of configuration, and just being PHP (much more
>>excited about working with PHP than I am perl)..
(checks PHPSlash folder)
They claim that's coming.
[snippage]
===
Subject: Re: [Slashcode] PHPSlash vs Slash..
From: Chris Nandor <pudge@pobox.com>
Date: Mon, 28 Feb 2000 15:06:38 -0500
At 14.53 -0500 2000.02.28, James Turinsky wrote:
>>At 13.44 -0500 2000.02.28, Chad Day wrote:
>>>PHPSlash is faster.
>>
>>I don't buy it. Slash is basically instantaneous in my machines. YMMV, I
>>suppose.
>
>
>Well, exactly *what* kind of machines are you using? SMP PIII's?
>Overclocked Athlons? You got 512MB RAM in those suckers?
One is a PowerPC G3/292 MHz with 160MB. Another is PIII/450 with 128MB, I
think, and the other is like a PIII/550 with about 512MB RAM. I also had
it on a PPro/200 with, I think, less than 100MB. That one was fine, but
only handled really small loads.
>I'll buy it on the grounds that mod_perl tends to suck a lot of RAM and on
>older machines (say a P-200 no MMX with the maximum 128MB EDO DRAM) you can
>start running outta RAM and into swap with good amounts of traffic.
Yeah, that is the main thing. You need RAM. If you have lotsa RAM, you
are fine. If you don't ... well, get more. :)
>Also PHP can be made --with-mysql which I believe ties in MySQL bits and
>pieces, as compared to calling other bits of Perl to talk to MySQL. PHP
>effectively becomes a MySQL client inside of Apache or something.
I don't know how that would speed anything up; mod_perl only needs to load
in the shared libraries for DBD::mysql and DBI once for each process, and
then it speeds right along. PHP might load into the process faster than
Perl, but I don't know if that is too relevant, when each process is
handling a couple of hundred requests anyway, and for each one that code is
already loaded in.
===
Subject: Re: [Slashcode] PHPSlash vs Slash..
From: atif@developer.ch
Date: Mon, 28 Feb 2000 21:23:16 +0100 (CET)
The ones that are baby-crying about PHP being faster and
cleaner, are script kiddies with no programming
background.
I have some at work here.
They are trying to hide behind PHP or others of the like
to hide the fact that they know nothing better.
The background of these kiddies is HTML, then
javascript, then maybe some ASP.
I think they should use the statement, \"PHP is EASIER an
more simpler to my brain\" :)
I have tested PHP, and wanted to implement it a bit on
our intranet (where currently a lot of apps are running
under modperl), so that new so called \"\"webdevelopers\"\"
can find something to do.
RAM/Hardware is not the issue (we have 1GB RAM per
server, not becuase the applications running on it need
so much , but because I have to run SETI on it :)
By the way: how do you split a string in an array in
PHP3? I could find a function in PHP4 but PHP3 dont have
something like that. Or did I not look enough?
PHP is not bad, but you cant compare PHP and mod_perl.
PHP is for kiddies, and mod_perl for grown-ups :)
So flame me now.
===
Subject: Re: [Slashcode] PHPSlash vs Slash..
From: "Christopher 'Gordo' Key" <knight13@uronramp.net>
Date: Mon, 28 Feb 2000 15:00:39 -0600 (CST)
On Mon, 28 Feb 2000 atif@developer.ch wrote:
//By the way: how do you split a string in an array in
//PHP3? I could find a function in PHP4 but PHP3 dont have
//something like that. Or did I not look enough?
array split(string pattern, string string, int [limit]);
ie
$array split(":",$passwd_line, 5);
First 5 fields from /etc/passwd where $passwd_line is a line
read in from /etc/passwd
B
//
//
//PHP is not bad, but you cant compare PHP and mod_perl.
//PHP is for kiddies, and mod_perl for grown-ups :)
No flames for you, just always amusing to watch people compare apples to
oranges.
Though to through my own in, to add "a little scripting" to an html page,
you do not need to code an entire script to print the page (as I've seen
with Perl) just put the snippet of code where you want the output in the
page (with PHP).
===