Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live on IIS6 [Answered]RSS

5 replies

Last post Oct 12, 2007 03:39 PM by rickjames

  • Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live on II...

    Oct 11, 2007 11:40 PM|chinayx|LINK

    Now when I set the cpu limit for a website using php on IIS6.0,I will get a error which say should not set cpu limit.

     

    cpu limit FastCGI Extension Go Live

  • Re: Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live o...

    Oct 12, 2007 01:20 AM|rickjames|LINK

    Hi chinayx,

    We use a JobObject to tie FastCGI processes to IIS. This prevents them (or their children) from establishing lives outside that of the worker process'. When the worker process disappears, so do all the FastCGI processes.

    The CPULimit feature also uses a JobObject.

    Unfortunately a process can only belong to one JobObject, making FastCGI and the CPULimit features mutually exclusive.

    Cheerz,

    Rick.

  • Re: Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live o...

    Oct 12, 2007 01:37 AM|chinayx|LINK

    thank you for your answer.

    and I have another question.

    How can I set a website's resouce limit.Because there are some website on my server.

    Can I do this with fcgiext.ini? 

  • Re: Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live o...

    Oct 12, 2007 11:19 AM|rickjames|LINK

    which resource are you trying to limit?

  • Re: Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live o...

    Oct 12, 2007 12:37 PM|chinayx|LINK

    cpu usage and connections in a special time

  • Re: Can I set a cpu limit for a website with FastCGI Extension for IIS6.0 and IIS5.1 - Go Live o...

    Oct 12, 2007 03:39 PM|rickjames|LINK

     Hi chinayx,

    CPU Limit and FastCGI features are mutually exclusive. This is not the end of the world, cause they can be configured for an application pool. Each application (e.g. /blog and /forums) can be served by different application pools. So you can continue to limit the cpu for non-FastCGI applications.

    The connection limits settings do not use a JobObject, and therefore don't have a bad interaction with FastCGI and should continue to work.

    Thanks,

    Rick.