Re: [google-appengine] Re: Node.js Standard: memory usage different for locally and deployed version on 30 - 40 Mb.

2018-06-23 Thread Aleksander Efremov
Ok. Will hope that will successful resolved soon. вс, 24 июн. 2018 г., 0:59 'George (Cloud Platform Support)' via Google App Engine : > Your issue warrants a more in-depth investigation. To facilitate > communication and tracking of progress, we have opened this issue >

Re: [google-appengine] Re: Node.js Standard: memory usage different for locally and deployed version on 30 - 40 Mb.

2018-06-26 Thread Aleksander Efremov
Hi George. That's ok. The main thing there is created issue. Thanks for helping. On Monday, June 25, 2018 at 1:14:21 AM UTC+4, George (Cloud Platform Support) wrote: > > Hello Aleksander, > > In fact there is no estimated time to resolution, but I am sure Developers > will address the issue as

[google-appengine] Re: Decline requests to the one GAE instance to use for them a other GAE instance

2018-07-02 Thread Aleksander Efremov
Thanks for a clear point here. On Monday, July 2, 2018 at 6:47:01 PM UTC+4, Jordan (Cloud Platform Support) wrote: > > It is not recommended to change the code that is currently running on a > single App Engine instance. Since App Engine scales its instances of your > application, >

[google-appengine] Node.js standard and urlfetch

2018-07-03 Thread Aleksander Efremov
All outbound requests in the "appengine" of "python" and "go" issue via "urlfetch" service. But for "node.js" it isn't available. There is improvements on using the "urlfetch" service instead of a native libraries in "python" and "go"? And why it isn't implemented for "node.js"? -- You

[google-appengine] Re: Node.js standard and urlfetch

2018-07-03 Thread Aleksander Efremov
I more want to know there are restrictions on fetching arbitrary URLs via "urlfetch" or "native libraries"? I rewrote the Go (was used the "urlfetch" service) implementation of the proxy service to Node.js (uses native http/https libraries) and I want to be sure a performance didn't change. On

Re: [google-appengine] Node.js Standard: memory usage different for locally and deployed version on 30 - 40 Mb.

2018-08-10 Thread Aleksander Efremov
Hi George. Thanks, I will try to follow your offer. пт, 10 авг. 2018 г., 21:52 'George (Cloud Platform Support)' via Google App Engine : > Hi Aleksander, > > If you speak about a different, even if somehow related issue, it is > better to open a separate discussion on that subject. As this

Re: [google-appengine] Re: Node.js Standard: memory usage different for locally and deployed version on 30 - 40 Mb.

2018-08-08 Thread Aleksander Efremov
Yes, it's better now, thanks. Before was difference from my PC and Cloud Platform about 20Mb, now 10Mb. On Wednesday, August 8, 2018 at 1:00:17 AM UTC+4, George (Cloud Platform Support) wrote: > > Hi Aleksander, > > The issue should be fixed by now; you are encouraged to test it again. > --

Re: [google-appengine] Re: Node.js Standard: memory usage different for locally and deployed version on 30 - 40 Mb.

2018-08-09 Thread Aleksander Efremov
I won't argue, it's enough for me. Thanks for helping. -- 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+unsubscr...@googlegroups.com. To

[google-appengine] Re: Node.js standard and urlfetch

2018-07-05 Thread Aleksander Efremov
t; > One advantage that urlfetch has is that it provides you with an interface > to make asynchronous requests > <https://cloud.google.com/appengine/docs/standard/python/issue-requests>. > > > > On Tuesday, July 3, 2018 at 2:01:26 AM UTC-4, Aleksander Efremov wrote: >> >

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-09 Thread Aleksander Efremov
for example by using the native `http` module. Did you > try it? > > Steren > Product Manager > App Engine > > On Sun, Jul 8, 2018 at 10:25 PM Aleksander Efremov > wrote: > >> oh, yes, it's important note, thanks. >> >> On Friday, July 6, 2018 at 6:58:38 P

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-10 Thread Aleksander Efremov
But yes, you're correct. Only for me is more important a streaming between the client and the my app. вт, 10 июл. 2018 г., 23:40 Aleksander Efremov : > > https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled > > Streaming Responses > > App Engin

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-10 Thread Aleksander Efremov
gt; > On Mon, 9 Jul 2018 at 22:11 Aleksander Efremov wrote: > >> Yes, I use `http`/`https` native libraries and I use streaming of course >> when it's possible. But as I understood from the AppEngine documentation, >> streaming doesn't work and all responses are buffered in

Re: [google-appengine] Re: Node.js standard and urlfetch

2018-07-08 Thread Aleksander Efremov
> > In Java8-land I've used both Apache HttpClient and OkHttp and both work > normally. > > Jeff > > On Thu, Jul 5, 2018 at 10:06 PM Aleksander Efremov > wrote: > >> Thanks, then I will star of course that feature request. And it's very >> good there isn't d

[google-appengine] Decline requests to the one GAE instance to use for them a other GAE instance

2018-06-29 Thread Aleksander Efremov
I use "Node.js" standard. Sometimes I need refresh "express.js" configuration. For it I should stop to accept a new requests, then wait while will resolved current requests and whether to restart the "express.js" or call "exit" GAE instance. How I can to notify the GAE manager that a new