Re: [PHP-DEV] Function caching... From: Jacob Verhoeks (jacob <email protected>)
Date: 12/09/00

On Friday 08 December 2000 23:36, you wrote:
> Jacob Verhoeks wrote:
> > The performance problem is not with executing but with the loading of the
> > code. We are currently developing a application server in php. That will
> > be loaded only once.
>
> The current performance limitations in PHP come from multiple
> design limitations.
>
> You already stated that the repeated compile is slowing down
> applications.

In our application we split the code in two.

1. The large code base
  Tis one is continually running deamon with the php4-cgi
  It's single thread and listens on a socket. (blocking)

  The frontend connects, sends the environment (url,post,get,cookie)
  the backend locates the action required by the user. Loads the template,
  execute all necessary functions.
  After then return it to the frontend

2. The light webbased frontend
   Small page with collectes the uri, get , post, cookie.
   Connects to the backend, send the environment.
   Waits for the result and returns that to the user.

   The backend can also set headers on the frontend
   
> The third problem is the indivisible user rights if you are
> running as a part of the web server, as Apache modules do. You
> always act as wwwrun. On the other hand, you are running in a
> different Apache module each time you are being called, making
> it impossible for you to reuse database connections, keeping
> cursors between calls and the like. That is, the process split
> of your web application is along the wrong lines.

We solved this in our backend by creating a persistant data array , that is
kept during the session

>
> I believe a Zend/PHP application server is sorely needed for
> the future growth of PHP. Some people in #php.de are coding at
> application servers written in PHP. These beasts communicate
> with the web server using shared memory. They aren't
> multithreaded which is why they need to prefork themselves,
> turning them into memory hogs. A proper native implementation is
> needed instead.
>

This looks like the same principe as we have (sockets agains shm).
But in our experience the single thread blocking server socket works fine and
has a great performance advantage.
3 pages/sec at a page with lot's of functions and database calls
to 20 pages/sec 

-- 
=  ing. Jacob Verhoeks    -   www.nedertux.com  =
=  Nedertux Technologies  -  jacob <email protected>  =

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>