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

[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 Cloud
> Functions problem looks more like a technical issue, rather than general or
> opinion-based, and needs fixing, it is better to open it in the Public
> Issue Tracker . It can get tracked
> easier there, and you may follow progress towards an eventual solution.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/fa9etnYlog0/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@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/45b7a227-7885-4c8d-814f-c6815752cad9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 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/CAGR2zgr9qi8RQYV_68R0TZg7bm8ieqXwcYntHRNJhtFpSimBQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 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/ff3ca4a0-e7fa-44f8-b231-fa78e1ad77b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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. 
>

-- 
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 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/49ba21c5-e055-484a-84eb-0e724957d2d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 Engine does not support streaming responses where data is sent in
> incremental chunks to the client while a request is being processed. All
> data from your code is collected as described above and sent as a single
> HTTP response.
>
> вт, 10 июл. 2018 г., 19:10 Jason Collins :
>
>> Streaming doesn't work for inbound requests (i.e., requests from a client
>> to your App Engine app), but should work fine for outbound requests
>> originating from your App Engine app to another server.
>>
>>
>> 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 any case. Do you
>>> know why streaming isn't ready yet and when it will possible?
>>>
>>>
>>> On Monday, July 9, 2018 at 6:49:18 PM UTC+4, Steren Giannini wrote:
>>>
>>>> Hi,
>>>>
>>>> As commented on the bug: It is not clear what problem a Node.js
>>>> implementation of urlfetch would solve.
>>>> Today, developers can use idiomatic methods to send asynchronous
>>>> requests to HTTP endpoints, 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 PM UTC+4, Jeff Schnitzer wrote:
>>>>>
>>>>>> There's one big disadvantage of the URLFetch service, which is that
>>>>>> it's limited to 32MB inbound and 10MB outbound. Those are pretty small
>>>>>> numbers in this day and age.
>>>>>>
>>>>>> 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 difference.
>>>>>>>
>>>>>>> On Thursday, July 5, 2018 at 11:58:27 PM UTC+4, Yasser Karout (Cloud
>>>>>>> Platform Support) wrote:
>>>>>>>>
>>>>>>>> Currently, there is no implementation of urlfetch for Node.js so
>>>>>>>> you would have to use the standard HTTP library
>>>>>>>> <https://nodejs.org/api/http.html> or other libraries to issue
>>>>>>>> HTTP requests.
>>>>>>>>
>>>>>>>> I created a feature request on the issue tracker website
>>>>>>>> <https://issuetracker.google.com/82003> which will get
>>>>>>>> forwarded to engineering. You can click on the star next to the request
>>>>>>>> title on the top of the page to mark that you are interested in the 
>>>>>>>> feature
>>>>>>>> and receive email updates.
>>>>>>>>
>>>>>>>> However there are no ETAs or guarantees of implementation for
>>>>>>>> feature requests.
>>>>>>>>
>>>>>>>> Regarding performance, all HTTP requests, whether urlfetch is used
>>>>>>>> or not, are issued using App Engine’s URL Fetch service
>>>>>>>> <https://developers.google.com/apps-script/reference/url-fetch/> for
>>>>>>>> efficiency and scaling purposes. Meaning performance will not differ 
>>>>>>>> while
>>>>>>>> using native libraries or urlfetch.
>>>>>>>>
>>>>>>>> One advantage that urlfetch has is that it provides you with an
>>>>>>>> interface to make asynchronous requests
>>>>>>>> <https://cloud.google.com/appengine/docs/s

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

[Aleksander Efremov]

https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled

Streaming Responses

App Engine does not support streaming responses where data is sent in
incremental chunks to the client while a request is being processed. All
data from your code is collected as described above and sent as a single
HTTP response.

вт, 10 июл. 2018 г., 19:10 Jason Collins :

> Streaming doesn't work for inbound requests (i.e., requests from a client
> to your App Engine app), but should work fine for outbound requests
> originating from your App Engine app to another server.
>
>
> 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 any case. Do you
>> know why streaming isn't ready yet and when it will possible?
>>
>>
>> On Monday, July 9, 2018 at 6:49:18 PM UTC+4, Steren Giannini wrote:
>>
>>> Hi,
>>>
>>> As commented on the bug: It is not clear what problem a Node.js
>>> implementation of urlfetch would solve.
>>> Today, developers can use idiomatic methods to send asynchronous
>>> requests to HTTP endpoints, 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 PM UTC+4, Jeff Schnitzer wrote:
>>>>
>>>>> There's one big disadvantage of the URLFetch service, which is that
>>>>> it's limited to 32MB inbound and 10MB outbound. Those are pretty small
>>>>> numbers in this day and age.
>>>>>
>>>>> 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 difference.
>>>>>>
>>>>>> On Thursday, July 5, 2018 at 11:58:27 PM UTC+4, Yasser Karout (Cloud
>>>>>> Platform Support) wrote:
>>>>>>>
>>>>>>> Currently, there is no implementation of urlfetch for Node.js so you
>>>>>>> would have to use the standard HTTP library
>>>>>>> <https://nodejs.org/api/http.html> or other libraries to issue HTTP
>>>>>>> requests.
>>>>>>>
>>>>>>> I created a feature request on the issue tracker website
>>>>>>> <https://issuetracker.google.com/82003> which will get
>>>>>>> forwarded to engineering. You can click on the star next to the request
>>>>>>> title on the top of the page to mark that you are interested in the 
>>>>>>> feature
>>>>>>> and receive email updates.
>>>>>>>
>>>>>>> However there are no ETAs or guarantees of implementation for
>>>>>>> feature requests.
>>>>>>>
>>>>>>> Regarding performance, all HTTP requests, whether urlfetch is used
>>>>>>> or not, are issued using App Engine’s URL Fetch service
>>>>>>> <https://developers.google.com/apps-script/reference/url-fetch/> for
>>>>>>> efficiency and scaling purposes. Meaning performance will not differ 
>>>>>>> while
>>>>>>> using native libraries or urlfetch.
>>>>>>>
>>>>>>> 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:
>>>>>>>>
>>>>>>>> All outbound requests in the "appengine" of "python" and "go" issue
>>>>>>>> via "urlfetch" service. But for &

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

[Aleksander Efremov]

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 any case. Do you 
know why streaming isn't ready yet and when it will possible?


On Monday, July 9, 2018 at 6:49:18 PM UTC+4, Steren Giannini wrote:
>
> Hi,
>
> As commented on the bug: It is not clear what problem a Node.js 
> implementation of urlfetch would solve.
> Today, developers can use idiomatic methods to send asynchronous requests 
> to HTTP endpoints, 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 PM UTC+4, Jeff Schnitzer wrote:
>>
>>> There's one big disadvantage of the URLFetch service, which is that it's 
>>> limited to 32MB inbound and 10MB outbound. Those are pretty small numbers 
>>> in this day and age.
>>>
>>> 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 difference.
>>>>
>>>> On Thursday, July 5, 2018 at 11:58:27 PM UTC+4, Yasser Karout (Cloud 
>>>> Platform Support) wrote:
>>>>>
>>>>> Currently, there is no implementation of urlfetch for Node.js so you 
>>>>> would have to use the standard HTTP library 
>>>>> <https://nodejs.org/api/http.html> or other libraries to issue HTTP 
>>>>> requests.
>>>>>
>>>>> I created a feature request on the issue tracker website 
>>>>> <https://issuetracker.google.com/82003> which will get forwarded 
>>>>> to engineering. You can click on the star next to the request title on 
>>>>> the 
>>>>> top of the page to mark that you are interested in the feature and 
>>>>> receive 
>>>>> email updates.
>>>>>
>>>>> However there are no ETAs or guarantees of implementation for feature 
>>>>> requests.
>>>>>
>>>>> Regarding performance, all HTTP requests, whether urlfetch is used or 
>>>>> not, are issued using App Engine’s URL Fetch service 
>>>>> <https://developers.google.com/apps-script/reference/url-fetch/> for 
>>>>> efficiency and scaling purposes. Meaning performance will not differ 
>>>>> while 
>>>>> using native libraries or urlfetch. 
>>>>>
>>>>> 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:
>>>>>>
>>>>>> 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 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-appengi...@googlegroups.com.
>>>> To post to this group, send email to google-a...@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/39c3df33-ceec-4af6-8204-c878b3ab9630%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/google-appengine/39c3df33-ceec-4af6-8204-c878b3ab9630%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>&

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

[Aleksander Efremov]

oh, yes, it's important note, thanks.

On Friday, July 6, 2018 at 6:58:38 PM UTC+4, Jeff Schnitzer wrote:
>
> There's one big disadvantage of the URLFetch service, which is that it's 
> limited to 32MB inbound and 10MB outbound. Those are pretty small numbers 
> in this day and age.
>
> 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 difference.
>>
>> On Thursday, July 5, 2018 at 11:58:27 PM UTC+4, Yasser Karout (Cloud 
>> Platform Support) wrote:
>>>
>>> Currently, there is no implementation of urlfetch for Node.js so you 
>>> would have to use the standard HTTP library 
>>> <https://nodejs.org/api/http.html> or other libraries to issue HTTP 
>>> requests.
>>>
>>> I created a feature request on the issue tracker website 
>>> <https://issuetracker.google.com/82003> which will get forwarded to 
>>> engineering. You can click on the star next to the request title on the top 
>>> of the page to mark that you are interested in the feature and receive 
>>> email updates.
>>>
>>> However there are no ETAs or guarantees of implementation for feature 
>>> requests.
>>>
>>> Regarding performance, all HTTP requests, whether urlfetch is used or 
>>> not, are issued using App Engine’s URL Fetch service 
>>> <https://developers.google.com/apps-script/reference/url-fetch/> for 
>>> efficiency and scaling purposes. Meaning performance will not differ while 
>>> using native libraries or urlfetch. 
>>>
>>> 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:
>>>>
>>>> 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 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-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@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/39c3df33-ceec-4af6-8204-c878b3ab9630%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/39c3df33-ceec-4af6-8204-c878b3ab9630%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 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/10f3f503-8b21-453f-80d4-acbe2d8e7e3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Aleksander Efremov]

Thanks, then I will star of course that feature request. And it's very good 
there isn't difference.

On Thursday, July 5, 2018 at 11:58:27 PM UTC+4, Yasser Karout (Cloud 
Platform Support) wrote:
>
> Currently, there is no implementation of urlfetch for Node.js so you would 
> have to use the standard HTTP library <https://nodejs.org/api/http.html> or 
> other libraries to issue HTTP requests.
>
> I created a feature request on the issue tracker website 
> <https://issuetracker.google.com/82003> which will get forwarded to 
> engineering. You can click on the star next to the request title on the top 
> of the page to mark that you are interested in the feature and receive 
> email updates.
>
> However there are no ETAs or guarantees of implementation for feature 
> requests.
>
> Regarding performance, all HTTP requests, whether urlfetch is used or not, 
> are issued using App Engine’s URL Fetch service 
> <https://developers.google.com/apps-script/reference/url-fetch/> for 
> efficiency and scaling purposes. Meaning performance will not differ while 
> using native libraries or urlfetch. 
>
> 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:
>>
>> 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 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 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/39c3df33-ceec-4af6-8204-c878b3ab9630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 Wednesday, July 4, 2018 at 9:00:20 AM UTC+4, Attila-Mihaly Balazs wrote:
>
> I believe (but I'm not 100%) that the new runtimes (node.js, Java 8, 
> Python 3.7 in beta, etc) are moving AppEngine standard more towards Flex. 
> Ie. they will be full containers (thought managed and updated by Google) 
> where you can install arbitrary binaries. This means that they don't/won't 
> need services like "urlfetch" because you can connect to arbitrary TCP/UDP 
> endpoints (though I'm sure there are/will be some restrictions like not 
> being able to send emails).
>
> All the best,
> Attila
>

-- 
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 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/a940b49e-ac6c-468b-aa0a-d6b75a4ece77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Node.js standard and urlfetch

[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 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 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/bb9bf64f-470f-4c57-92b9-60ab7b0f1c9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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, 
> 
>  
> that single instance may turn down due to low traffic, and you would lose 
> any changes persisted on that instance. Likewise, new instances created due 
> to higher traffic will not posses the change you made (since it was only 
> local to that single instance). Additionally you cannot control which 
> instance a request will run on. 
>
> It is therefore recommended to directly deploy a new App Engine version 
> 
>  
> with your code change, and then migrate your traffic to the new version 
> .
>  
> This way no requests will be made to your new version until you deploy it 
> and/or migrate traffic to it (as deploying may actually migrate traffic for 
> you automatically). Once deployed, all requests will now see your 
> configuration change and run on the new code. 
>
> - Note that Google Groups  
> is reserved for general discussions. If you require technical support for 
> performing the above it is recommended to post your detailed questions 
>  to Stack Exchange 
>  using the supported 
> Cloud tags. 
>

-- 
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 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/6cde09bf-e766-4aac-bea0-408fa3dea650%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 requests impossible to 
process still on this GAE instance?

-- 
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 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/6de31ff5-5f4b-48f2-8a1d-6f78ed272431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 soon as possible, taken into account their 
> priorities. 
>

-- 
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 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/e68bb92a-fd1a-478c-8736-ebb873660008%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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
>  in the Public Issue Tracker.
> You may monitor it for further developments. There is no estimated time to
> resolution as yet.
>
> --
> 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 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/08c4333a-d3c6-41a0-b6db-e2df363e2abb%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 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/CAGR2zgrp%3D1zdEkrtBSOop-hdEQBLinwAyawcdGnNG%3DOi_AJ4Mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.