Announcement

Collapse
No announcement yet.

What is causing - PHP has encountered an Access Violation at 7C8224B2?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    phplens version is rather buggy on Windows 2003 SP2 in our testing (around 15 million hits a month, one server, latest PHP).

    The MS implementation may not be final, but it certainly is reliable (and yes, it is beta... afaik).

    CGI and FastCGI both create new processes for requests - but you must be mistaken - FastCGI does not create a new process for each request - it reuses the same process. It creates multiple process for multiple simultaneous requests (up till a point where it "queues" them in a line to use existing processes). CGI on the other hand, creates and kills a new process for each connection, making it a billion times less efficient than FastCGI and a million times less than ISAPI.

    Of course this isn't ideal and that's why ISAPI is great - but PHP doesn't give a damn about Windows' users and have labeled this as a "low priority" "known issue" with regards to "poor stability/reliability on Windows"

    It's up to you. You can boost performance for 10 minutes by using ISAPI - until your server is brought crashing down to its heels by un-threadsafe extensions (basically everything that ships with PHP) or you can use FastCGI and sacrifice a bit of performance for a ton of stability.
    NeoSmart Technologies
    http://neosmart.net/forums/

    Comment


    • #17
      Originally posted by Computer Guru View Post
      phplens version is rather buggy on Windows 2003 SP2 in our testing (around 15 million hits a month, one server, latest PHP).

      The MS implementation may not be final, but it certainly is reliable (and yes, it is beta... afaik).

      CGI and FastCGI both create new processes for requests - but you must be mistaken - FastCGI does not create a new process for each request - it reuses the same process. It creates multiple process for multiple simultaneous requests (up till a point where it "queues" them in a line to use existing processes). CGI on the other hand, creates and kills a new process for each connection, making it a billion times less efficient than FastCGI and a million times less than ISAPI.

      Of course this isn't ideal and that's why ISAPI is great - but PHP doesn't give a damn about Windows' users and have labeled this as a "low priority" "known issue" with regards to "poor stability/reliability on Windows"

      It's up to you. You can boost performance for 10 minutes by using ISAPI - until your server is brought crashing down to its heels by un-threadsafe extensions (basically everything that ships with PHP) or you can use FastCGI and sacrifice a bit of performance for a ton of stability.
      Watching the process list, FastCGI created so many processes that there wasn't a sacrifice of a "bit of performance" the server was unusable.

      Yes, ISAPI is not very stable for me right now. But at least people can get to the pages.
      PowWows.com

      Comment

      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
      Working...
      X