PHP and a lengthy process (Python, Java, etc.)?

I would like your opinion on writing web applications in PHP and a lengthy process using tools like Django or Turbogears for Python.

As far as I know: - In PHP, pages are extracted from the hard drive every time (although I assume that the OS stores files in RAM some time after they were available) - Pages are recompiled into the operation code every time (although tools, for example, Zend can store the compiled version in RAM) - Getting pages every time means reading global data and session data every day and reopening database connections

So, I believe that PHP makes sense on a shared server (multiple sites sharing the same host) to run applications with moderate use, while a lengthy process provides better performance for applications running on a dedicated server and under heavy use?

Thanks for any feedback.

+5
source share
5 answers
  • With APC , which will soon be included by default in PHP, the compiled bytecode is stored in RAM.
  • With mod_php, which is the most popular way to use PHP, the PHP interpreter stays in the memory of the web server.
  • APC memcache, , , , , .

.

+2

, memcache, opcode , PHP , PHP , , , , .

PHP , . ( ), concurrency .

, , , ( ?) : , , , . , .

. , . - concurrency , .

+2

PHP , , . , . PHP- - eAccelerator.

+1

, PHP Django . - PHP , . Django.

/ .

0

PHP - , Java .. - php, JVM! MAX-Runtime PHP- - ( - ).

, . , (CPU-Time, RAM) , /Vserver/Shared Host!

eAccelerator .. Apache ! . mod_dbd. (, ), , memcached!

-1

All Articles