Correct it only checks the one file with check being measured in microseconds. The whole queuing time from Apache accept() to start of request handling in daemon process would itself be less than a millisecond. Both figures are insignificant in context of how long it takes for application code and database queries to run. So would suggest it is a non issue in the grander scheme of things especially when you consider that from browser side total page times average up to six seconds based on New Relic blog post just out about end user monitoring statistics.
Graham On 18/06/2011, at 10:44 AM, Carl Nobile <[email protected]> wrote: > If my understanding is correct mod_wsgi only checks the hook file. > Matter-of-fact that means if you touch this file mod_wsgi will reload all > other files--great for development, but onlu in daemon mode. In the usual > case mod_wsgi will not look at any files other than the hook file--it loads > all files into memory the first time around then never looks at them again > unless of cause you change or touch the hook file or reload Apache. > > Graham could go into more specifics about this I am sure. > > ~Carl > > On Fri, Jun 17, 2011 at 8:02 PM, Guy <[email protected]> wrote: > I've searched the web but can't find any references to the following > question which leads me to ask it here. Can anyone tell me if there's > any notable performance hit due to mod_wsgi's reload behaviour when it > reads the timestamp of the .wsgi application file and reloads the app > if it has changed? > > I'm fairly new to the world of mod_wsgi and this question comes from > my experience using PHP's APC module, which has a directive that can > disable file checking on each request (apc.stat). I have no idea if > mod_wsgi operates in the same way, but it would seem to me that it > must do a filesystem check in order to identify if the timestamp has > changed. If someone could confirm or disconfirm this I'd appreciate > it. > > Thanks, > Guy > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > > > > -- > ------------------------------------------------------------------------------- > Carl J. Nobile (Software Engineer) > [email protected] > ------------------------------------------------------------------------------- > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
