php-windows Digest 19 Oct 2011 21:26:23 -0000 Issue 3977
Topics (messages 30715 through 30721):
Re: PHP 64-bit binaries?
30715 by: Pierre Joye
30716 by: Lester Caine
30717 by: Ferenc Kovacs
30718 by: Pierre Joye
30719 by: Lester Caine
30720 by: Lester Caine
junk from my forms output
30721 by: hanson zhou
Administrivia:
To subscribe to the digest, e-mail:
php-windows-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-windows-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-wind...@lists.php.net
----------------------------------------------------------------------
--- Begin Message ---
On Mon, Oct 17, 2011 at 9:38 AM, Lester Caine <les...@lsces.co.uk> wrote:
> Yes Pierre - on the larger systems we run multiple machines, but on sites
> that only require a single computer, a single clean stack is also nice, with
> everything in the one base directory and without the agro of deciding if
> this is a 32bit or 64bit program. Everything running on the Linux boxes is
> 64 bit, and everything is built from the same code base, so I will continue
> to use a single 64bit stack ..
We are not talking about a linux stack here. And a server, even on the
same machine, has nothing to do with the clients connecting to it, as
explained earlier already.
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
--- End Message ---
--- Begin Message ---
Pierre Joye wrote:
Yes Pierre - on the larger systems we run multiple machines, but on sites
> that only require a single computer, a single clean stack is also nice, with
> everything in the one base directory and without the agro of deciding if
> this is a 32bit or 64bit program. Everything running on the Linux boxes is
> 64 bit, and everything is built from the same code base, so I will continue
> to use a single 64bit stack ..
We are not talking about a linux stack here. And a server, even on the
same machine, has nothing to do with the clients connecting to it, as
explained earlier already.
? I'm running the full stack on windows as 64 bit code and seeing a performance
improvement over the 32bit version. Stripping parts out of the 64 bit stack and
just running them 32bit may be worth the effort, but *I* am happy that my own
PHP section running 64bit libraries for graphics and eaccelerator is running
faster than switching just that section to 32 bit. There way well be room for
improvement, but having to sort out which programs can be 64bit and which 32bit
is just messy. Apache running 64 bit IS faster so using a 32 bit version once
one switches to VC9 builds, so maintaining everything 64bit VC9 just seems
sensible. Exactly the same as it is on Linux anyway.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--- End Message ---
--- Begin Message ---
On Mon, Oct 17, 2011 at 10:46 AM, Lester Caine <les...@lsces.co.uk> wrote:
> Pierre Joye wrote:
>
>> Yes Pierre - on the larger systems we run multiple machines, but on sites
>>> > that only require a single computer, a single clean stack is also
>>> nice, with
>>> > everything in the one base directory and without the agro of deciding
>>> if
>>> > this is a 32bit or 64bit program. Everything running on the Linux
>>> boxes is
>>> > 64 bit, and everything is built from the same code base, so I will
>>> continue
>>> > to use a single 64bit stack ..
>>>
>> We are not talking about a linux stack here. And a server, even on the
>> same machine, has nothing to do with the clients connecting to it, as
>> explained earlier already.
>>
>
> ? I'm running the full stack on windows as 64 bit code and seeing a
> performance improvement over the 32bit version.
we are talking about your whole stack, as you didn't ran benchmarks using
32bit php vs 64bit php.
> Stripping parts out of the 64 bit stack and just running them 32bit may be
> worth the effort,
yeah, using 32bit php should gain you a little bit performance gain, and
more stable and supported build.
> but *I* am happy that my own PHP section running 64bit libraries for
> graphics and eaccelerator is running faster than switching just that section
> to 32 bit.
how do you know that it is running faster? did you benchmarked it against
the 32bit version? I thought that you didn't.
> There way well be room for improvement, but having to sort out which
> programs can be 64bit and which 32bit is just messy.
yeah, life is a bitch.
> Apache running 64 bit IS faster
are you sure?
I didn't really see any benchmarks supporting that fact, let alone for
windows, which is usually less of an interest for the apache httpd
developers.
> so using a 32 bit version once one switches to VC9 builds, so maintaining
> everything 64bit VC9 just seems sensible. Exactly the same as it is on Linux
> anyway.
yeah, if you are using php as an apache module, but if you use for example
fastcgi, you can run 32bit php with 64bit apache or vice versa.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
--- End Message ---
--- Begin Message ---
On Mon, Oct 17, 2011 at 10:46 AM, Lester Caine <les...@lsces.co.uk> wrote:
> Pierre Joye wrote:
>>>
>>> Yes Pierre - on the larger systems we run multiple machines, but on sites
>>> > that only require a single computer, a single clean stack is also
>>> > nice, with
>>> > everything in the one base directory and without the agro of deciding
>>> > if
>>> > this is a 32bit or 64bit program. Everything running on the Linux
>>> > boxes is
>>> > 64 bit, and everything is built from the same code base, so I will
>>> > continue
>>> > to use a single 64bit stack ..
>>
>> We are not talking about a linux stack here. And a server, even on the
>> same machine, has nothing to do with the clients connecting to it, as
>> explained earlier already.
>
> ? I'm running the full stack on windows as 64 bit code and seeing a
> performance improvement over the 32bit version. Stripping parts out of the
> 64 bit stack and just running them 32bit may be worth the effort
Quoting your last mail:
" Everything running on the Linux boxes is 64 bit, and everything is
built from the same code base, so I will continue to use a single
64bit stack ..". So let stop this confusing discussion, points have
been made, we have ran extensive tests with all possible apps and
backends, PHP is actually slower and not stable enough and in some
extend less safe when built as 64bit. And I refer only to PHP and its
libraires here, not external tools like databases.
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
--- End Message ---
--- Begin Message ---
Ferenc Kovacs wrote:
? I'm running the full stack on windows as 64 bit code and seeing a
performance improvement over the 32bit version.
we are talking about your whole stack, as you didn't ran benchmarks using 32bit
php vs 64bit php.
I haven't rolled back just part ... in fact I have yet to find 32 bit builds of
some of the extensions I use, but see last note ...
Stripping parts out of the 64 bit stack and just running them 32bit may be
worth the effort,
yeah, using 32bit php should gain you a little bit performance gain, and more
stable and supported build.
but *I* am happy that my own PHP section running 64bit libraries for
graphics and eaccelerator is running faster than switching just that section
to 32 bit.
how do you know that it is running faster? did you benchmarked it against the
32bit version? I thought that you didn't.
I've not rolled back to 32bit with 5.3.8 ... the base benchmark was back at
5.3.5 time frame, although I'm not seeing any difference between 5.3.7 and 5.3.8
on 64bit speed wise.
Apache running 64 bit IS faster
are you sure?
Fairly ... but I've just wiped the 32bit vista machine and that will have a
clean 64bit W7 next so I've got another chance to get the figures.
I didn't really see any benchmarks supporting that fact, let alone for windows,
which is usually less of an interest for the apache httpd developers.
Anindya builds both x86 and x64 versions of Apache with VC9 since there are no
official builds of Apache we can use with PHP anyway, so complaining that I'm
not using an official PHP is a little academic anyway :) I'll run in just the
Apache first and play with that - but my benchmarks are on PHP :(
so using a 32 bit version once one switches to VC9 builds, so maintaining
everything 64bit VC9 just seems sensible. Exactly the same as it is on Linux
anyway.
yeah, if you are using php as an apache module, but if you use for example
fastcgi, you can run 32bit php with 64bit apache or vice versa.
I only ever use php5apache2_2.dll in Apache ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--- End Message ---
--- Begin Message ---
Pierre Joye wrote:
On Mon, Oct 17, 2011 at 10:46 AM, Lester Caine<les...@lsces.co.uk> wrote:
Pierre Joye wrote:
Yes Pierre - on the larger systems we run multiple machines, but on sites
that only require a single computer, a single clean stack is also
nice, with
everything in the one base directory and without the agro of deciding
if
this is a 32bit or 64bit program. Everything running on the Linux
boxes is
64 bit, and everything is built from the same code base, so I will
continue
to use a single 64bit stack ..
We are not talking about a linux stack here. And a server, even on the
same machine, has nothing to do with the clients connecting to it, as
explained earlier already.
? I'm running the full stack on windows as 64 bit code and seeing a
performance improvement over the 32bit version. Stripping parts out of the
64 bit stack and just running them 32bit may be worth the effort
Quoting your last mail:
" Everything running on the Linux boxes is 64 bit, and everything is
built from the same code base, so I will continue to use a single
64bit stack ..". So let stop this confusing discussion, points have
been made, we have ran extensive tests with all possible apps and
backends, PHP is actually slower and not stable enough and in some
extend less safe when built as 64bit. And I refer only to PHP and its
libraires here, not external tools like databases.
"so I will continue to use a single 64bit stack .. " on Windows since my
starting point is the 64 bit build of Apache using php5apache2_2.dll built from
the same code base as the 64 bit Linux stack ...
Since there are no 'official' VC9 builds of Apache we are starting from an
unofficial base anyway.
It would be useful to know where you are seeing stability issues since I have
yet to find any and have a number of fairly busy sites running on it. These are
all intranet, so have had quite a hammering from the IT departments security
wise without any failures, but are not accessible outside the network.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--- End Message ---
--- Begin Message ---
I have the following in a file called "hello.php" in my htdocs directory
(Apache webroot).
<form action="action.php" method="post">
<p>Your name: <input type="text" name="name" /></p>
<p>Your age: <input type="text" name="age" /></p>
<p><input type="submit" /></p>
</form>
as well as the following in a file "action.php", also in the same directory.
Hi <?php echo htmlspecialchars($_POST['name']); ?>.
You are <?php echo (int)$_POST['age']; ?> years old.
When I click on the submit button of the form in hello.php, it should say
something like:
"Hi Hanson. You are 33 years old." But instead of just saying that it also
appends a bunch of junk at the beginning like this:
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0
Arial;}} {\*\generator Msftedit 5.41.21.2509;}\viewkind4\uc1\pard\f0\fs20 Hi
hanson .\par You are 33 years old.\par } �
Can someone help me with this? Why does my forms reply from action.php
contain so much junk? I have a Windows installation of PHP and Apache.
thanks,
-Hanson
--- End Message ---
