Status Update
No update yet.
Comments
va...@google.com
fr...@gmail.com
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
ku...@google.com
Hello,
Thank you for coming back and providing the additional information.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
fr...@gmail.com
I'm glad that Google is giving the importance that this matter deserves due
to the drastic reduction in cpu per instance.
Thanks!
Francisco Reis
On Tue, Oct 3, 2023, 3:51 PM <buganizer-system@google.com> wrote:
fr...@gmail.com
Hello,
I think it is time to have a conclusion on this issue.
Also in Java 21 Runtime.getRuntime().availableProcessors() continues to show 1 processor while for Java 8 it was always 8 processors.
Are we really paying 8 times more for processors/cores in Java 17 and 21 than we were in Java 8? With no warning whatsoever from your side?
Francisco Reis
Description
I was surprised that AppEngine Java 17 gives us 1 core per instance.
I expected that the 8 cores/threads per instance of AppEngine Java 8 would be maintained.
This seams like a drastic, and may I say inadmissible, reduction for the same price.
I attach information for Java 17 and Java 8 obtained by my instances.