--------------------------------------------
On Sun, 12/11/16, castle.sandie via Google App Engine 
<[email protected]> wrote:

 Subject: Re: [google-appengine] Re: Instance restart
 To: [email protected]
 Date: Sunday, December 11, 2016, 3:37 PM
 
 
 --------------------------------------------
 On Sun, 12/11/16, Joshua Fox <[email protected]>
 wrote:
 
  Subject: Re: [google-appengine] Re: Instance restart
  To: [email protected]
  Date: Sunday, December 11, 2016, 3:18 PM
  
  I
  don't understand the value proposition of the Flex
  Environment, especially the non-compat one.
  It does not support AppEngine APIs,
  Memcache, or built-in credentials. Scaling is nice, and
  there are some management tools, but is that enough reason
  for users to adopt it, in contrast to an IaaS or container
  solution?
  
  I am asking a
  high-level question here: Why would a software architect,
  seeing a variety  of choices for building an application
  (beyond a standard webapp or pipeline), choose to use
  Flexible Environment?
  On Mon, Dec 5, 2016 at 8:15
  PM, 'George (Cloud Platform Support)' via Google App
  Engine <[email protected]>
  wrote:
  Hello
  Stefano, 
  When
  you say that after the deprecation of the compat java
  flexible runtime one is force to come back to the standard
  environment, you might have overlooked one of the
  alternatives. This
  excellent alternative would be the
  flexible
  environment,
  that offers some services similar to the standard
  environment, especially important among these being
  scalability.
  You can
  simply
  adapt
  your app to the Flexible Environment using
  Google
  Cloud Client libraries.
  
  If
  you decide to keep your application running in the
 standard
  environment, there are a few avenues leading to improved
  latency.
  
  Firstly,
  your code seems to take the bulk of the response time, one
  sees 17746 ms for yap/action/
 TecDocGenericArticlesGetAction
  (Timestamp 2016-12-05 (12:12:20.790)). By contrast, Google
  platform services provide about 2 ms reaction time.
  
  The
  app.yaml settings you have chosen can be fine tuned too.
 The
  two main parameters are min pending latency of 0.500 ms,
  that can be increased, and Max Concurrent Request set to 5
  when the default is 50. Playing around with these 2
  parameters may improve latency markedly, and avoid the
  launching of new instances, but the main source of delay
  seems to be somewhere in your code. 
  
  
  
  -- 
  
  You received this message because you are subscribed to
 the
  Google Groups "Google App Engine" group.
  
  To unsubscribe from this group and stop receiving emails
  from it, send an email to google-appengine+unsubscribe@
  googlegroups.com.
  
  To post to this group, send email to google-appengine@googlegroups.
  com.
  
  Visit this group at https://groups.google.com/
  group/google-appengine.
  
  To view this discussion on the web visit https://groups.google.com/d/
  msgid/google-appengine/ a5594b85-a03b-455d-a523-
  0c4cfd58f3d0%40googlegroups. com.
  
  For more options, visit https://groups.google.com/d/
  optout.
  
  
  
  
  -- 
  JOSHUA FOX
  Principal Software Architect |
  Freightos
  
  ☏ (Israel): +972-545691165 | ☏ (US):  +1-3123400953 |
 Skype: joshuafox.freightosSmoother shipping with
  the world's online freight marketplace.
  Online Marketplace / In the News / Freightos Blog
  
  
  
  
  
  -- 
  
  You received this message because you are subscribed to
 the
  Google Groups "Google App Engine" group.
  
  To unsubscribe from this group and stop receiving emails
  from it, send an email to [email protected].
  
  To post to this group, send email to [email protected].
  
  Visit this group at
 https://groups.google.com/group/google-appengine.
  
  To view this discussion on the web visit
 
https://groups.google.com/d/msgid/google-appengine/CAD%3DB7cOwO5B58zd7_qRv-ot7HFJ3_%2BoVEHnnhrKT-OO6oUdpYA%40mail.gmail.com.
  
  For more options, visit
 https://groups.google.com/d/optout.
  eoarece au sperat sa obtina mari profituri  dupa 1949
 comunistii si-au intensificat prezenta in lumea
 satelor  spre a-i sili pe tarani  prin toate
 mijloacele  de cele mai multe ori violente  sa
 intre in gospodariile colective. incepea
 colectivizarea  un proces punctat de grave abuzuri si
 violente  care au trezit
 
 -- 
 You received this message because you are subscribed to the
 Google Groups "Google App Engine" group.
 To unsubscribe from this group and stop receiving emails
 from it, send an email to [email protected].
 To post to this group, send email to [email protected].
 Visit this group at
 https://groups.google.com/group/google-appengine.
 To view this discussion on the web visit
 
https://groups.google.com/d/msgid/google-appengine/76317496.573979.1481463448490%40mail.yahoo.com.
 For more options, visit
 https://groups.google.com/d/optout.upa 1958 se constata o relansare in -Gursa 
catre un stalinism rigid. Ea a fost legata de neintelegerile cu Uniunea 
Sovietica pe tema integrarii economice a statelor socialiste in C.A.E.R. Acesta 
a determinat o politica de industrializare fortata a carei baza s-a dorit a fi 
industria siderurgica  chimica  si constructoare de masini. Astfel s-a nascut 
si dezvoltat combinatul de la Galati  intretinut insa  din greu  pe baza 
importului de minereu de fier.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1540607185.695261.1481477711760%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to