This is the system limit info:
http://linux.about.com/library/cmd/blcmdl2_setrlimit.htm
It has nothing to do with PHP.
The PHP limit is in the INI file and you can grep for that INI parameter in
PHP. But again, it is something which is managed inside the Zend memory
manager (zend_alloc.*)
Andi
Andi Gutmans wrote:
This is the system limit info:
http://linux.about.com/library/cmd/blcmdl2_setrlimit.htm
this 8M limit is linux ?
It has nothing to do with PHP.
The PHP limit is in the INI file and you can grep for that INI parameter in
PHP.
Sure , let us say there's no line memory_l
Andi Gutmans wrote:
There is no hardcoded counting. We either cound (--enable-memory-limit) or
we don't (i.e. we rely on the system limits)
Andi
-Original Message-
From: bertrand Gugger [mailto:[EMAIL PROTECTED]
btw , could you and PHP archives the same , avoid to quote direct emai
Andi Gutmans wrote:
There is no hardcoded counting. We either cound (--enable-memory-limit) or
we don't (i.e. we rely on the system limits)
OK , I guess I have to find out where this php , constant , system wide
limit is.
I thought the 8M limit was due to PHP , is it C doing it ?
Thanks for th
There is no hardcoded counting. We either cound (--enable-memory-limit) or
we don't (i.e. we rely on the system limits)
Andi
> -Original Message-
> From: bertrand Gugger [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 29, 2006 1:10 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-D
The MSSQL extension can be linked against FreeTDS (php_dblib.dll on Win32).
This removes all the limitations that exists in ntwdblib.
- Frank
> As far as I know, and I might be wrong, ASP.NET uses a managed runtime
.NET
> interface which does not use COM (It's the actual TDS protocol
implemented
Andi Gutmans wrote:
Hi Bertrand,
The discussion is on how and what we count, not on whether to count or not.
The quoted discussion is/was , this one is about the possibility to get
16M without counting.
If you count in 256KB increments instead of in byte increments then there's
less counting t
As far as I know, and I might be wrong, ASP.NET uses a managed runtime .NET
interface which does not use COM (It's the actual TDS protocol implemented
in managed code). COM is viewed as poor way to run such interfaces both for
performance reasons and resource reference counting resources.
Andi
>
Hi Bertrand,
The discussion is on how and what we count, not on whether to count or not.
If you count in 256KB increments instead of in byte increments then there's
less counting to do in order to get to 16MB :)
Andi
> -Original Message-
> From: bertrand Gugger [mailto:[EMAIL PROTECTED]
Bonsoir,
I sure bore the list , but I still miss something.
There was that thread about "memory_get_usage with new Memory Manager"
where Ilia (et al.) evocated the overhead induced by the
memory_get_usage() and family functions.
as , e.g. , in http://marc.theaimsgroup.com/?l=php-dev&m=115400370
Hi Andi,
ASP.NET is using OLEDB, as well, and in my experiences this does not add
to much penalty to communicating with MSSQL (however obviously more
exhaustive performance tests are required). However I am wondering
whether the OLEDB way would still work on non-Windows PHP versions? If
not:
Hi Chung,
Any idea on the performance of OLEDB? My understanding was that due to it
going through the COM layer, performance will be relatively poor.
Any idea?
Andi
> -Original Message-
> From: Chung Leong [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 28, 2006 2:37 PM
> To: internals
Hi,
Also it does seem NUL char safe?
php -r "$var='3'.chr(0).'foo'; var_dump(filter_data($var,
FILTER_VALIDATE_INT));"
int(3)
Jared
> -Original Message-
> From: Pierre [mailto:[EMAIL PROTECTED]
> Sent: 28 July 2006 17:44
> To: Kevin Waterson
> Cc: internals@lists.ph
Hi again,
OK, after my last message, I found when the dec*() functions started
converting to unsigned long (Bug #6761). To make dechex(~8) etc. work. Now
I know that behavior can't change. :-) Hopefully this is my last e-mail
about this, if I can please find out about 2 simple things:
1) How s
14 matches
Mail list logo
