php-general Digest 25 Apr 2013 14:29:46 -0000 Issue 8209
php-general Digest 25 Apr 2013 14:29:46 - Issue 8209 Topics (messages 320986 through 320988): Re: Load testing an app 320986 by: Andrew Ballard 64bit php5.5.0beta3 on Windows 320987 by: Jan Vávra Re: Updated PHP breaks processing-intense Procedure 320988 by: Ken Kixmoeller Administrivia: To subscribe to the digest, e-mail: php-general-digest-subscr...@lists.php.net To unsubscribe from the digest, e-mail: php-general-digest-unsubscr...@lists.php.net To post to the list, e-mail: php-gene...@lists.php.net -- ---BeginMessage--- On Apr 24, 2013 9:46 PM, tamouse mailing lists tamouse.li...@gmail.com wrote: On Tue, Apr 23, 2013 at 8:04 AM, Andrew Ballard aball...@gmail.com wrote: On Tue, Apr 23, 2013 at 2:29 AM, Adam Richardson simples...@gmail.com wrote: On Mon, Apr 22, 2013 at 10:41 PM, Andrew Ballard aball...@gmail.com wrote: The other developer in our office spent some time profiling the site with xdebug and found that an exec() call to netsh used on a couple pages seems to take 2-4 seconds to complete. Unfortunately, those exec() calls are the one function that we cannot test in our development environment. I'm wondering if it would be possible to carve out the part doing the netsh calls so they're not part of your web application's stack, and make them an asynchronous part? Possibly, but it needs to be as close as possible to real time. We've been looking into caching the results for a short time (15sec?) so concurrent requests can share results. The problem right now is that we can't seem to duplicate the issue we were having, so it's impossible to know for sure whether any solution we try actually solves the problem. Andrew ---End Message--- ---BeginMessage--- Hello, I've tried VC11 x64 Thread Safe (2013-Apr-10 17:40:00) downloaded from http://windows.php.net/qa/ and I've called filesize on 4,25 GB file. This call failed with Warning: filesize(): stat failed Then I printed values of echo PHP_INT_SIZE.\n; echo PHP_INT_MAX.\n; 4 2147483647 This is weird. I've expected working filesize and values 8, 2 ^63. Jan. ---End Message--- ---BeginMessage--- THank all of you for your help. I think I got this thing licked. On Wed, Apr 24, 2013 at 7:14 PM, Ken Kixmoeller phph...@comcast.net wrote: Thank you very much, Jim --- On Wed, Apr 24, 2013 at 5:34 PM, Jim Lucas li...@cmsws.com wrote: On 04/24/2013 03:24 PM, Ken Kixmoeller wrote: Thanks, Jim --- Is this different from the max_input_vars discussion above? (from David OBrien) yes. For example... php.ini:[suhosin] php.ini:;suhosin.log.syslog = php.ini:;suhosin.log.syslog.**facility = php.ini:;suhosin.log.syslog.**priority = php.ini:;suhosin.log.sapi = php.ini:;suhosin.log.script = php.ini:;suhosin.log.phpscript = 0 php.ini:;suhosin.log.script.**name http://suhosin.log.script.name = php.ini:; variables registered in the current scope: SUHOSIN_ERRORCLASS and php.ini:; SUHOSIN_ERROR. The first one is the alert class and the second variable is php.ini:;suhosin.log.**phpscript.name http://suhosin.log.phpscript.name= php.ini:;suhosin.log.**phpscript.is_safe = Off php.ini:;suhosin.log.use-x-**forwarded-for = Off php.ini:;suhosin.executor.max_**depth = 0 php.ini:;suhosin.executor.**include.max_traversal = 0 php.ini:;suhosin.executor.**include.whitelist = php.ini:;suhosin.executor.**include.blacklist = php.ini:;suhosin.executor.**func.whitelist = php.ini:;suhosin.executor.**func.blacklist = php.ini:;suhosin.executor.**eval.whitelist = php.ini:;suhosin.executor.**eval.blacklist = php.ini:;suhosin.executor.**disable_eval = Off php.ini:;suhosin.executor.**disable_emodifier = Off php.ini:; by default in Suhosin = 0.9.6. Allowing symlink() while open_basedir is used php.ini:;suhosin.executor.**allow_symlink = Off php.ini:; If you fear that Suhosin breaks your application, you can activate Suhosin's php.ini:; simulation mode with this flag. When Suhosin runs in simulation mode, php.ini:;suhosin.simulation = Off php.ini:; first. It always uses resource slot 0. If Suhosin got this slot assigned APC php.ini:; will overwrite the information Suhosin stores in this slot. When this flag is php.ini:; set Suhosin will request 2 Slots and use the second one. This allows working php.ini:;suhosin.apc_bug_**workaround = Off php.ini:;suhosin.sql.bailout_**on_error = Off php.ini:;suhosin.sql.user_**prefix = php.ini:;suhosin.sql.user_**postfix = php.ini:;suhosin.multiheader = Off php.ini:suhosin.mail.protect = 1 php.ini:; memory_limit to whatever value they want. Suhosin changes this fact and php.ini:; that Suhosin will disallows scripts setting the memory_limit to a value above php.ini:;suhosin.memory_limit = 0 php.ini:suhosin.session.**encrypt = Off php.ini:;suhosin.session.**cryptkey = php.ini:;suhosin.session.**cryptua = On
[PHP] 64bit php5.5.0beta3 on Windows
Hello, I've tried VC11 x64 Thread Safe (2013-Apr-10 17:40:00) downloaded from http://windows.php.net/qa/ and I've called filesize on 4,25 GB file. This call failed with Warning: filesize(): stat failed Then I printed values of echo PHP_INT_SIZE.\n; echo PHP_INT_MAX.\n; 4 2147483647 This is weird. I've expected working filesize and values 8, 2 ^63. Jan. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Updated PHP breaks processing-intense Procedure
THank all of you for your help. I think I got this thing licked. On Wed, Apr 24, 2013 at 7:14 PM, Ken Kixmoeller phph...@comcast.net wrote: Thank you very much, Jim --- On Wed, Apr 24, 2013 at 5:34 PM, Jim Lucas li...@cmsws.com wrote: On 04/24/2013 03:24 PM, Ken Kixmoeller wrote: Thanks, Jim --- Is this different from the max_input_vars discussion above? (from David OBrien) yes. For example... php.ini:[suhosin] php.ini:;suhosin.log.syslog = php.ini:;suhosin.log.syslog.**facility = php.ini:;suhosin.log.syslog.**priority = php.ini:;suhosin.log.sapi = php.ini:;suhosin.log.script = php.ini:;suhosin.log.phpscript = 0 php.ini:;suhosin.log.script.**name http://suhosin.log.script.name = php.ini:; variables registered in the current scope: SUHOSIN_ERRORCLASS and php.ini:; SUHOSIN_ERROR. The first one is the alert class and the second variable is php.ini:;suhosin.log.**phpscript.name http://suhosin.log.phpscript.name= php.ini:;suhosin.log.**phpscript.is_safe = Off php.ini:;suhosin.log.use-x-**forwarded-for = Off php.ini:;suhosin.executor.max_**depth = 0 php.ini:;suhosin.executor.**include.max_traversal = 0 php.ini:;suhosin.executor.**include.whitelist = php.ini:;suhosin.executor.**include.blacklist = php.ini:;suhosin.executor.**func.whitelist = php.ini:;suhosin.executor.**func.blacklist = php.ini:;suhosin.executor.**eval.whitelist = php.ini:;suhosin.executor.**eval.blacklist = php.ini:;suhosin.executor.**disable_eval = Off php.ini:;suhosin.executor.**disable_emodifier = Off php.ini:; by default in Suhosin = 0.9.6. Allowing symlink() while open_basedir is used php.ini:;suhosin.executor.**allow_symlink = Off php.ini:; If you fear that Suhosin breaks your application, you can activate Suhosin's php.ini:; simulation mode with this flag. When Suhosin runs in simulation mode, php.ini:;suhosin.simulation = Off php.ini:; first. It always uses resource slot 0. If Suhosin got this slot assigned APC php.ini:; will overwrite the information Suhosin stores in this slot. When this flag is php.ini:; set Suhosin will request 2 Slots and use the second one. This allows working php.ini:;suhosin.apc_bug_**workaround = Off php.ini:;suhosin.sql.bailout_**on_error = Off php.ini:;suhosin.sql.user_**prefix = php.ini:;suhosin.sql.user_**postfix = php.ini:;suhosin.multiheader = Off php.ini:suhosin.mail.protect = 1 php.ini:; memory_limit to whatever value they want. Suhosin changes this fact and php.ini:; that Suhosin will disallows scripts setting the memory_limit to a value above php.ini:;suhosin.memory_limit = 0 php.ini:suhosin.session.**encrypt = Off php.ini:;suhosin.session.**cryptkey = php.ini:;suhosin.session.**cryptua = On php.ini:;suhosin.session.**cryptdocroot = On php.ini:;suhosin.session.**cryptraddr = 0 php.ini:; session. The difference to suhosin.session.cryptaddr is, that the IP is not php.ini:;suhosin.session.**checkraddr = 0 php.ini:;suhosin.cookie.**encrypt = 0 php.ini:;suhosin.cookie.**cryptkey = php.ini:;suhosin.cookie.**cryptua = On php.ini:;suhosin.cookie.**cryptdocroot = On php.ini:;suhosin.cookie.**cryptraddr = 0 php.ini:; cookie. The difference to suhosin.cookie.cryptaddr is, that the IP is not php.ini:;suhosin.cookie.**checkraddr = 0 php.ini:;suhosin.cookie.**cryptlist = php.ini:;suhosin.cookie.**plainlist = php.ini:; Defines the reaction of Suhosin on a filter violation. php.ini:;suhosin.filter.action = php.ini:;suhosin.cookie.max_**array_depth = 50 php.ini:;suhosin.cookie.max_**array_index_length = 64 php.ini:;suhosin.cookie.max_**name_length = 64 php.ini:;suhosin.cookie.max_**totalname_length = 256 php.ini:;suhosin.cookie.max_**value_length = 1 php.ini:;suhosin.cookie.max_**vars = 100 php.ini:;suhosin.cookie.**disallow_nul = 1 php.ini:;suhosin.get.max_**array_depth = 50 php.ini:;suhosin.get.max_**array_index_length = 64 php.ini:;suhosin.get.max_name_**length = 64 php.ini:;suhosin.get.max_**totalname_length = 256 php.ini:;suhosin.get.max_**value_length = 512 php.ini:;suhosin.get.max_vars = 100 php.ini:;suhosin.get.disallow_**nul = 1 php.ini:;suhosin.post.max_**array_depth = 50 php.ini:;suhosin.post.max_**array_index_length = 64 php.ini:;suhosin.post.max_**name_length = 64 php.ini:;suhosin.post.max_**totalname_length = 256 php.ini:suhosin.post.max_**value_length = 2048000 php.ini:suhosin.post.max_vars = 500 php.ini:;suhosin.post.**disallow_nul = 1 php.ini:;suhosin.request.max_**array_depth = 50 php.ini:;suhosin.request.max_**array_index_length = 64 php.ini:;suhosin.request.max_**totalname_length = 256 php.ini:suhosin.request.max_**value_length = 2048000 php.ini:;suhosin.request.max_**vars = 200 php.ini:;suhosin.request.max_**varname_length = 64 php.ini:;suhosin.request.**disallow_nul = 1 php.ini:;suhosin.upload.max_**uploads = 25 php.ini:;suhosin.upload.**disallow_elf = 1 php.ini:;suhosin.upload.**disallow_binary = 0 php.ini:;suhosin.upload.**remove_binary = 0
Re: [PHP] PHP compiler - HipHop performance
On Fri, Apr 26, 2013 at 1:56 PM, Norah Jones nh.jone...@gmail.com wrote: Hi, I have downloaded HipHop for my website, I am going through various web links which are suggesting that performance will improve 3-6 times. However I don't know the Stability of the HipHop. Please provide your inputs so that I can decide to use HipHop. Thanks, Norah Jones -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php I looked into HipHop once, and I decided not to use it, I felt that there are other ways of improving performance. Having said that, it really depends on what your running IE wordpress, phpbb, mybb etc. I rather install some cache plugin for wordpress and install something like xcache but that just me though.
