How are you identifying that it's reloading?
If the load is really light, the instance might just be timing out and
getting killed before a 2nd request comes in.
On Sep 16, 4:55 am, Микола <[EMAIL PROTECTED]> wrote:
> Yes, we have main() function.
>
> On 15 Вер, 22:56, Tony Arkles <[EMAIL PROTE
Hi,
we see messages about requests taking almost 30 time more time then usual to
process (in GAE console) that happen during load of application (many
modules, several Mb in zip).
Additionally global structures of application are being reset (meaning old
one was "killed").
Is timeout (exceeding
> How are you identifying that it's reloading?
We use own zipimporter and when some imports done - it logs that.
> If the load is really light, the instance might just be timing out and
> getting killed before a 2nd request comes in.
First load is very hard (imports are done from big archive (wit
Sorry, by "light load" I mean "infrequent traffic". If there is only
1 request every few minutes, it's not likely that GAE will be keeping
an instance of your app in memory. As traffic increases, you're much
more likely to have your app stay running.
12MB worth of modules does seem pretty large
Is it 12MB of code or are you using modules to store data? If it's code
then it might be possible to look at only importing the modules as they're
needed. If it's data it might be beter to work out how to get it into the
datastore and only access the bits you need when you need them.
I would firs
> Is it 12MB of code or are you using modules to store data?
Yes. It is code.
> If it's code then it might be possible to look at only importing the modules
> as they're needed.
It is impossible because we pack in that way framework. Our
application is little but it uses that framework.
On 17 Вер
>I would first try to find a way to avoid loading the 12MB because you can't
>rely on it staying in memory between requests.
Yes, but the question is - why GAE reloads application without any
warnings, when application don't use many resourses, and why at the
same time it don't reload http://code
On Sep 17, 6:04 am, Микола <[EMAIL PROTECTED]> wrote:
> >I would first try to find a way to avoid loading the 12MB because you can't
> >rely on it staying in memory between requests.
>
> Yes, but the question is - why GAE reloads application without any
> warnings, when application don't use ma
Yes, maybe you are right.
On Sep 17, 4:18 pm, Wooble <[EMAIL PROTECTED]> wrote:
> On Sep 17, 6:04 am, Микола <[EMAIL PROTECTED]> wrote:
>
> > >I would first try to find a way to avoid loading the 12MB because you
> > >can't rely on it staying in memory between requests.
>
> > Yes, but the questi
Hi,
Will there be any indication in the logs that application crashed with
segmentation fault?
We'll try to simulate moderate load level and see if it is GAE "unload"
policy due to size of application.
Regards,
m.
2008/9/17 Wooble <[EMAIL PROTECTED]>
>
>
>
> On Sep 17, 6:04 am, Микола <[EMAIL
This is purely for curiosity sake... what framework are you using that
is 12MB zipped up?
On Sep 17, 7:57 am, Микола <[EMAIL PROTECTED]> wrote:
> Yes, maybe you are right.
>
> On Sep 17, 4:18 pm, Wooble <[EMAIL PROTECTED]> wrote:
>
> > On Sep 17, 6:04 am, Микола <[EMAIL PROTECTED]> wrote:
>
> >
> what framework are you using that is 12MB zipped up?
Zope3
it is ziped with compression level 0 for faster loading
On Sep 17, 6:05 pm, Tony Arkles <[EMAIL PROTECTED]> wrote:
> This is purely for curiosity sake... what framework are you using that
> is 12MB zipped up?
>
> On Sep 17, 7:57 am, Мико
On Sep 17, 10:50 am, "Myroslav Opyr" <[EMAIL PROTECTED]> wrote:
> Will there be any indication in the logs that application crashed with
> segmentation fault?
Considering the python sandbox doesn't really let you do low-level
monkeying around with memory, if you're managing to segfault the thin
13 matches
Mail list logo
