Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100258 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98454 invoked from network); 19 Aug 2017 22:15:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Aug 2017 22:15:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:29799] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/0A-34801-B98B8995 for ; Sat, 19 Aug 2017 18:15:56 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3xZZ6036tqzXMZ for ; Sun, 20 Aug 2017 00:15:52 +0200 (CEST) To: internals@lists.php.net References: Message-ID: Date: Sun, 20 Aug 2017 00:15:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 8 (or earlier) RFC Proposal From: lists@rhsoft.net ("lists@rhsoft.net") Am 19.08.2017 um 16:28 schrieb Admin NxPoint: > I would like to know your opinion on an RFC I'm thinking to propose. > > I don't have the skills to code this into PHP Core so anyone who would like > to be involved is welcomed. > > The RFC would refer to PHP's ability to use either SWAP memory and/or SWAP > Files. > > There are some very interesting things that PHP knows how to do, related to > data-processing, filtering, regex and so on, but one of the main blockers > is the "memory limit". > > There are servers or situation where memory can't be extended, but where > disk space is available and maybe even fast enough (SSD) to cover that gap. > > At this moment PHP doesn't know how to use the SWAP memory from linux, and > there isn't any way to specify a file that could act as one, similar to an > internal PHP SWAP PHP itself has no business to deal with swap or even know that swap exists at all - thats the natural core business of teh underlying operating system and userland has not to try outsmart the OS