Revision history [back]
Most likely it is due to the way you deployed.
Please check - are you serving media from Python? (all media should be served by a webserver directly)
Is your system swapping memory?
Initial startup - just the first hit will take longer due to compilation and determination whether you changed media, currently we do it by calculating hash of the content of the media dirs, there may be a faster way to do it. If you have multiple processes - each will consume extra time on response to the first web request.
Most likely it is due to the way you deployed.
Please check - are you serving media from Python? (all media should be served by a webserver directly)
Is your system swapping memory?
Initial startup - just the first hit will take longer due to compilation and determination whether you changed media, currently we do it by calculating hash of the content of the media dirs, there may be a faster way to do it. If you have multiple processes - each will consume extra time on response to the first web request.startup.
Most likely it is due to the way you deployed.
Please check - are you serving media from Python? (all media should be served by a webserver directly)
Is your system swapping memory?
Initial startup - just the first hit will take longer due to compilation and determination whether you changed media, currently we do it by calculating hash of the content of the media dirs, there may be a faster way to do it. If you have multiple processes - each will consume extra time on startup.it.