Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33077
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hyves.nl designates 217.170.2.100 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8238E.678970A9"
Date: Sat, 10 Nov 2007 12:39:50 +0100
Message-ID: <AD5924F6A589EF419765D39834C6BAFE348C11@hyves1.exchange.cysonet.com>
Thread-Topic: [PHP-DEV] Making parallel database queries from PHP
Thread-Index: AcgjhNElPVKTYwORTcqJEpukzKZoyAACMtg8
References: <e5fac5430711091727n7ce26594scb9b31f1f3babc1e@mail.gmail.com> <cd5680a20711100231n7ccdb2c2i878dd5b9f54f057f@mail.gmail.com>
To: <internals@lists.php.net>
Cc: "Alexey Zakhlestin" <indeyets@gmail.com>
Subject: RE: [PHP-DEV] Making parallel database queries from PHP
From: arend@hyves.nl ("Arend van Beelen")

------_=_NextPart_001_01C8238E.678970A9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

While I can see the theoretical advantage of this, I wonder how much =
there's too gain in practice (at least for us, that is).

In our current codebase, when a database query is done, PHP can only =
continue when it has the result anyway, so it would require serious code =
modifications to make use of such functionality. Also, while it may =
theoratically shorten page load times, our webservers are already =
constraint by CPU load anyway, so we would probably not be able to get =
more pageviews out of it either.

-----Oorspronkelijk bericht-----
Van: Alexey Zakhlestin [mailto:indeyets@gmail.com]
Verzonden: za 10-11-2007 11:31
Aan: Arend van Beelen
CC: internals@lists.php.net
Onderwerp: Re: [PHP-DEV] Making parallel database queries from PHP
=20
I would prefer to have some function, which would check, if the
requested data is already available (if it is not, I would still be
able to do something useful, while waiting)

On 11/10/07, Arend van Beelen <arend@hyves.nl> wrote:
> Hi there,
>
> I am researching the possibility of developing a shared library which =
can
> perform database queries in parallel to multiple databases. One =
important
> requirement is that I will be able to use this functionality from PHP.
> Because I know PHP is not thread-safe due to other libraries, I am =
wondering
> what would be the best way to implement this. Right now I can imagine =
three
> solutions:
>
> - Use multiple threads to connect to the databases, but let the =
library
> export a blocking single-threaded API. So, PHP calls a function in the
> library, this function spawns new threads, which do the real work. =
Meanwhile
> the function waits for the threads to finish, and when all threads are =
done
> it returns the final result back to PHP.
> - Use a single thread and asynchronous socket communication. So, PHP =
calls
> the library function and this function handles all connections within =
the
> same thread using asynchronous communication, and returns the result =
to PHP
> when all communication is completed.
> - Use a daemon on the localhost. Make a connection from PHP to the =
daemon,
> the daemon handles all the connections to the databases and passes the
> result back to the connection made from PHP.
>
> Can someone give me some advise about advantages of using one approach =
or
> another? Please keep in mind that I'm hoping for a solution which will =
be
> both stable and minimizes overhead.
>
> Thanks,
> Arend.
>
> --
> Arend van Beelen jr.
> "If you want my address, it's number one at the end of the bar."
>


--=20
Alexey Zakhlestin
http://blog.milkfarmsoft.com/



------_=_NextPart_001_01C8238E.678970A9--