[google-appengine] Re: Appengine Latency

Hi, When deploying using Java 7, the initial spin up time for a new instance is 2.6 s, whereas for Java 8 is even worst, 5.8 s. https://issuetracker.google.com/issues/67992784 Regards On Wednesday, 20 December 2017 02:06:23 UTC-2, Sourav Chandra wrote: > > > We are using appengine with java7.

[google-appengine] Re: GAE roadmap

Hi Samuel, There is no roadmap, unfortunately. What I did to predict a small portion of what is coming next was a filter inside public bugtracker for *Accepted* feature requests: https://issuetracker.google.com/issues?q=componentid:187191%2B%20status:accepted But you won't get any ETA. Regard

[google-appengine] Java url-stream-handler: native vs urlfetch

What are the advantages and disadvantages while using *native* vs *urlfetch* ? It is known that *urlfetch* doesn't need billing enabled and you can also use it in order to identity your app to apis and services . In theory, bec

[google-appengine] Re: Spring Framework on GAE Standard Java 8 / Remote API in Thread

I've seen this a few times when trying to use AppIdentity apis from request scoped threads. But on my case the issue happened because GAE was killing the thread as it can't outlive the request. Try using appengine background threads

[google-appengine] Re: Appengine Dashboard: Instances (created, active, billed)

Thanks Jordan but I am still a bit confused with the relation between *Active* and *Billed Estimate*. Please check if below affirmatives are correct: - Instance will be counted as *Active* if it was processing at least one user request on the exact time statistic was collected. - Insta

[google-appengine] Appengine Dashboard: Instances (created, active, billed)

I am trying to understand the difference between created, active and billed estimate from attached graph. This project has exactly 17 microservices and before may 23rd they were all manual scaled instances, one for each service. By 23rd I've enabled auto scaling for them all and it started coun

[google-appengine] Re: Cold boot on appengine with java8 takes longer time when compared to java7

34 UTC-3, Nilson Pontello wrote: > > I've deployed the helloworld samples on appegine standard using *java7* > and *java8* runtimes and noticed that *java8* takes in average *6 times > longer* to spin up a new instance. I've used *B1* instances on my tests > but noticed

[google-appengine] Re: Cold boot on appengine with java8 takes longer time when compared to java7

Hi George, I've tried everything, including servlet 3.1, enableQuickstart, enableJarClasses, enableJarSplitting, etc... I can't reduce *java8* startup time for a simple hello world servlet to be as fast as *java7*. 1. Have you reproduced it from your side? 2. Should I consider that *java

Re: [google-appengine] Re: Best practicies for making GAE microservices idempotent

ance of duplicate task delivery. > > BTW I can't recall the named task deduplication ever failing when > enqueuing a task. > On Mon, Oct 9, 2017 at 4:48 AM Nilson Pontello > wrote: > >> Thanks Jason/George, >> >> My code does a job very similar to lock.py &

[google-appengine] Re: Best practicies for making GAE microservices idempotent

Thanks Jason/George, My code does a job very similar to lock.py (this is what I am trying to avoid). So it looks like the secret is around task queues. Can I assume that enqueued tasks will be delivered *just once *(if my en

[google-appengine] Best practicies for making GAE microservices idempotent

Hi everyone, I have an event driven architecture built on top of google cloud pubsub. Because it guarantees At-Least-Once Delivery , my subscribers are required to be idempotent when processing messages. The only way I've

[google-appengine] Re: App Engine Pricing for auto scaling instances

gt; contains wrong info is is leading to the confusion. Regards On Thursday, 5 October 2017 14:19:06 UTC-3, Nilson Pontello wrote: > > Hi Everyone, > > From this link <https://cloud.google.com/appengine/pricing> I found the > below: > > Instances running in *manual*

[google-appengine] App Engine Pricing for auto scaling instances

Hi Everyone, >From this link I found the below: Instances running in *manual* and *basic* scaling services are billed at > hourly rates based on uptime. Billing begins when an instance starts and > ends fifteen minutes after a manual instance shuts

[google-appengine] Re: Primeiro deploy

Olá Stenio, Você precisa copiar o codigo que aparece no console da sua aplicação e colar na pagina que abre automaticamente no navegador. Não uso netbeans mas da uma olhada no console da aplicação que o codigo vai estar lá. Uma outra opção é rodar *gcloud auth init* na mão e seguir os passos.

[google-appengine] Cold boot on appengine with java8 takes lomnger than java7 (standard)

I've deployed the helloworld samples on appegine standard using java7 and java8 runtimes and noticed that java8 takes in average 6 times longer to spin up a new instance. I've used B1 instances on my tests but noticed the same on B2 as well and I am not willing to use more expensive instance cl

[google-appengine] Cold boot on appengine with java8 takes longer time when compared to java7

I've deployed the helloworld samples on appegine standard using *java7* and *java8* runtimes and noticed that *java8* takes in average *6 times longer* to spin up a new instance. I've used *B1* instances on my tests but noticed the same on *B2* as well and I am not willing to use more expensive