On Oct 24, 10:31 am, Gijsbert wrote:
> Does anybody know if the start time of java apps are significantly
> better (since they are compiled)?
>
The Java apps also take several seconds to start.
Frankly, I consider that WAY FAST.
Java server-side APIs are very heavyweight and definitely designe
On Oct 22, 1:22 pm, gae123 wrote:
>
> you bring up a lot of good points but I was wondering what triggered
> your e-mail and what makes you believe that we are actually in this
> sort of "destructive cycle"?
>
Devel63 stated in his opening message that his/her application was
being cycled out
On Oct 22, 10:55 am, Devel63 wrote:
>
> Speeding up cold starts is clearly the best solution, but I don't know
> how much time pre-compiling would save. Paying for warm instances may
> help, but because anyone can auto-ping every second, the tragedy of
> the commons will still proceed to its i
On Oct 21, 10:31 pm, Devel63 wrote:
>
> I see only 2 ways out:
>
Another way would be for Google to charge to keep applications warm.
Amazon has a similar feature where you can pay extra to reserve EC2
instances to make sure that the instance are always available.
Keeping apps warm is quite re
On Oct 14, 7:05 am, Jonathan wrote:
>
> I looked through a couple of pages of the requests, and there are a
> lot of issues that I care about (and starred). There are issues there
> that are "New" from more than a year ago. How can it be that Google is
> taking no notice of this communication c
On Sep 15, 6:04 pm, ryan wrote:
>
> i also feel your pain in the support department. we wish we had the
> resources to provide more high-touch support! we're not a large team,
> though, so we have to ruthlessly prioritize. that often means less
> individual support, and it can also means priori
On Sep 8, 2:58 pm, David Given wrote:
> Adligo wrote:
> > I mentioned is stored as a Session Attribute. I assume that the app
> > engine must be
> > keeping the Session in a location that can be accessed by all
> > threads.
>
> I'm afraid not!
>
> The *only* mechanism for communicating between
On Sep 2, 4:25 pm, "Brandon N. Wirtz" wrote:
>
> Is anyone actually hitting Thread limit errors? Or is this just a typical
> I'm going to be the next Facebook OMG Google won't work for this when I get
> to 1.2m active users guess I should build my own server in my basement
> because it will be
On Sep 2, 2:34 pm, "Brandon N. Wirtz" wrote:
> What would you need all those threads for in a web App? If you were
> crunching DNA, or calculating the path of particles from the big bang that
> would make sense...
>
When you make an asynchronous URLFetch call does each asynchronous
call to UR
Since the inefficiency is in the encoding of an Entity to a Protocol
Buffer should I assume that the advice to use an unindexed array
instead of an unindexed List also applies to the Java environment??
On Sep 1, 6:56 am, "Nick Johnson (Google)"
wrote:
> > Why do you advice using ArrayProperty i
Hi Jeff,
A question
Can I assume that the memcache size limit will increase as the number
of servers running my application increases?
On Aug 10, 5:53 pm, "Jeff S (Google)" wrote:
>
> The overall memcache size limit is not set in stone so we usually don't give
> a hard number as whatever
Actually, I meant 'coherent', not consistent.
On Aug 4, 1:24 pm, ted stockwell wrote:
> ...in other words, is it possible for memcache to develop a 'split
> brain' without notifiying its clients that something bad has happened?
--~--~-~--~~~---
...in other words, is it possible for memcache to develop a 'split
brain' without notifiying its clients that something bad has happened?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To p
ited two
working days for a response.
I really need someone to release me from my SMS Verification
purgatory.
Thanks in advance,
-ted stockwell
PS: I think I somehow got into this state because, for reasons I don't
understand, it seems to have taken several hours for the SMS
verificatio
14 matches
Mail list logo
