Status Update
Comments
dn...@google.com <dn...@google.com> #2
7a...@gmail.com <7a...@gmail.com> #3
7a...@gmail.com <7a...@gmail.com> #4
According to Amy:
10 - Java
10 - Go
8 - Python
> this limit should be determined dynamically, based on past performance. making it configurable is a second-best solution.
That's seems reasonable. Actually, based on new information I'm wondering if the limited couldn't be removed entirely.
According to @proppy's answer on stackoverflow:
There are 4 factors that go into determining, whether or not an instance may take on an additional request.
1. The current number of requests is < 10 (8 with Python27)
2. Instance Memory utilization < soft Memory limit
3. Instance CPU utilization < class CPU limit
4. The instance is warming up
The original justification for the N=10 request limit was to prevent instance from out-of-memory death:
Since instance memory & CPU utilization are now determining factors; could the N=10 limit be removed? Are there other considerations? If the soft memory limit doesn't provide an adequate buffer - is there a way to determine average memory usage per request? If so, maybe that could be used to adjust the buffer.
Thoughts?
ri...@google.com <ri...@google.com>
bo...@google.com <bo...@google.com>
hs...@google.com <hs...@google.com> #5
kr...@gmail.com <kr...@gmail.com> #6
hs...@google.com <hs...@google.com> #7
kr...@gmail.com <kr...@gmail.com> #8
jo...@gmail.com <jo...@gmail.com> #9
jm...@gmail.com <jm...@gmail.com> #10
Where do those numbers come from for Python and Java? Are they documented anywhere?
ma...@gmail.com <ma...@gmail.com> #11
Currently I'm having to code around this (batch requests up so that each request spawns it's own background threads), but this is something that I shouldn't have to do.
ra...@gmail.com <ra...@gmail.com> #12
I'd like to set at 15 or 20 instead of spinning up new instances which then service 1 request each and shut down because the first and longest running instance is happily servicing further requests.
Alternatively if Google is improving the instance startup to prevent this issue, perhaps using past instance/server performance metrics (thus making this configuration option redundant) I'd like to know.
jo...@gmail.com <jo...@gmail.com> #13
sh...@gmail.com <sh...@gmail.com> #14
"The max_concurrent_requests setting is now configurable per version/module. [link to this issue]"
I cannot see any mention of this new configuration either in my GAE/J Administration Console application settings or in the GAE/J documentation. Either it's there and I have missed it, or it isn't there yet.
I trust that, if missing, access to this new setting will be added and documented.
hs...@google.com <hs...@google.com> #16
The Java configuration documentation link above concerns app modules, not apps in general, and in particular a new "max-concurrent-requests" tag.
I still cannot see a setting for my app in the Administration Console, nor can I see anything in the Java application (non-module) configuration documentation.
da...@gmail.com <da...@gmail.com> #17
da...@gmail.com <da...@gmail.com> #18
Also, again according to the GAE/J documentation, modules and their configuration are still in preview, so it would seem a little strange to me that an existing configuration method is depreciated before its replacement is out of preview.
[Deleted User] <[Deleted User]> #19
<automatic-scaling>
<max-concurrent-requests>50</max-concurrent-requests>
</automatic-scaling>
What it will actually do is configure the 'default module' of your application. Note that those settings can't coexist with the Administration Console Performance settings, so once you do the switch: you will have to configure performance settings using appengine-web.xml.
jo...@gmail.com <jo...@gmail.com> #20
sh...@gmail.com <sh...@gmail.com> #21
se...@gmail.com <se...@gmail.com> #22
I agree with that. The severity and priority of this issue should be increased.
[Deleted User] <[Deleted User]> #23
By the way, probably you guys are dealing with this with your own ways, but in my case the only way I found to keep working was using my real phone for testing the apps (through adb), and using WSL2 in the pc
ri...@gmail.com <ri...@gmail.com> #24
Reply to #18:
Thank you very much. Your change makes AVD with Hyper-V work on my AMD 5950X.
ma...@gmail.com <ma...@gmail.com> #25
Worked for me also! THANKS!
mi...@gmail.com <mi...@gmail.com> #26
Could you share patched qemu-system-x86_64.exe, please?
Thanks a lot.
ri...@gmail.com <ri...@gmail.com> #27
Reply to #26:
Binary files with #18 changes that compiled by me:
Extract to <ANDROID_SDK>/emulator/qemu/windows-x86_64
.
mi...@gmail.com <mi...@gmail.com> #28
Thank you, I can confirm that this patched version perfectly works with all W11 Hyper-V & Core Isolation features turned on.
rs...@gmail.com <rs...@gmail.com> #29
Thanks for the binaries finally the emulator is working on AMD Ryzen 5950 with WSL2 under Windows 11.
Note: They require to update Android Emulator (30.9.5) first which is not automatically offered when using the Android SDK Manager of Visual Studio
da...@gmail.com <da...@gmail.com> #30
Just a note that I hope is helpful: You can get the 30.9.5 update for the Emulator with the Visual Studio Android SDK Manager by clicking the gear icon, selecting "Repository" -> "Full List (Unsupported)". Once you do that, you should see available updates for the Android Emulator component to get from 30.8.4 to 30.9.5.
I'm glad to see that this change is also working for people with AMD CPUs... I don't have one so I couldn't test it. :-)
[Deleted User] <[Deleted User]> #31
Now works fine for me in Windows 11, AMD Ryzen 7 5800H
jm...@gmail.com <jm...@gmail.com> #32
I can also confirm that the patched version posted by #27 does work.
Windows 11 22000.282 and AMD R9 5900HS.
zr...@gmail.com <zr...@gmail.com> #33
jo...@gmail.com <jo...@gmail.com> #34
Google, any updates on this issue from your side? Can you apply the same fix and ship it through Android Studio?
hs...@google.com <hs...@google.com> #35
Microsoft confirmed the issue was related to xsave. And we are working on emulator update based on Microsoft's suggestions.
ku...@gmail.com <ku...@gmail.com> #36
cr...@gmail.com <cr...@gmail.com> #37
C:\Program Files (x86)\Android\android-sdk\emulator\qemu\windows-x86_64
Please, do that *after* updating your emulator to 30.9.5, since the installer might try to "fix" your installation and get rid of any manually copied files.
ro...@gmail.com <ro...@gmail.com> #38
Why is it a P2, shouldn't it be a P1 or P0 ?
ry...@gmail.com <ry...@gmail.com> #39
th...@bellwethercorp.com <th...@bellwethercorp.com> #40
C:\Users\USERNAME\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64
It immediately started working. Thank you so much, hopefully this fix will get baked in at some point.
ry...@gmail.com <ry...@gmail.com> #41
hs...@google.com <hs...@google.com> #42
Anyone can try emulator 31.1.2 and see if it fixes the issue. The fix is basically the same as #18 but only remove "disable xsave" on Windows 11.
da...@gmail.com <da...@gmail.com> #43
da...@gmail.com <da...@gmail.com> #44
Hi, I have been running this with a build from the repo code at 2c6ba8d (a few commits after the bump to v31.1.2) for the last 5 days, approx 2-3 hours a day, and it has worked well on my i7-1185g7 on Windows 11.
Is there an internal/nightly build you would like me to test instead? Or would you like me to rebuild at the bump commit (f6a220d) ?
You can email me directly if that is easier. I'm happy to help, just let me know...
Thanks,
Daniel
(author of #18)
hs...@google.com <hs...@google.com> #45
Thanks for offering help. It would be perfect to run at 2c6ba8d. Actually to my surprise (I am not the one working on releases), I just found that our emulator binary 31.1.2 might not be compiled at exactly the bump commit but rather a few commits after. So your build is actually very close to emulator binary 31.1.2.
It does seem my commit can fix the problem from your test results.
Thanks!
hs...@google.com <hs...@google.com>
ma...@gmail.com <ma...@gmail.com> #46
bo...@google.com <bo...@google.com> #47
try to use canary channel in studio's sdk manager, 31.1.2 should show up.
bo...@google.com <bo...@google.com> #49
je...@gmail.com <je...@gmail.com> #50
bo...@google.com <bo...@google.com> #51
ja...@gmail.com <ja...@gmail.com> #52
ha...@gmail.com <ha...@gmail.com> #53
Edition Windows 11 Pro
Version 21H2
Installed on 10/5/2021
OS build 22000.318
Experience Windows Feature Experience Pack 1000.22000.318.0
da...@gmail.com <da...@gmail.com> #54
From your log it appears WHPX initializes successfully:
WHPX on Windows 10.0.22000 detected.
Windows Hypervisor Platform accelerator is operational
Further down we see:
ERROR | It seems too many emulator instances are running on this machine. Aborting.
I believe this is caused by an issue opening the network ports for ADB connections.
In my logs, I will have this where yours fails:
VERBOSE | control console listening on port 5554, ADB on port 5555
If you don't have something using the ports already, you may need to configure your firewall rule or something similar. Google search the "too many emulator instances" error message text and you should be able to find more information...
Hope this helps.
mw...@gmail.com <mw...@gmail.com> #55
PS C:\Users\mlwp\Software\Android\emulator> .\emulator.exe -avd Pixel_C_API_30 -show-kernel
INFO | Android emulator version 31.1.2.0 (build_id 7869535) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO | added library vulkan-1.dll
INFO | configAndStartRenderer: setting vsync to 60 hz
ERROR | Failed to open /qemu.conf, err: 2
WHPX on Windows 10.0.22000 detected.
Windows Hypervisor Platform accelerator is operational
INFO | Started GRPC server at
INFO | Advertising in: C:\Users\mlwp\AppData\Local\Temp\avd\running\pid_12832.ini
[ 5497.725387] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 5497.727452] rcu: 1-...!: (0 ticks this GP) idle=ffc/0/0x0 softirq=62892/62892 fqs=1 last_accelerate: d2d8/d3ec, Nonlazy posted: ..D
[ 5497.727452] (detected by 0, t=21015 jiffies, g=160085, q=10509)
[ 5497.727452] Sending NMI from CPU 0 to CPUs 1:
[ 5497.755413] NMI backtrace for cpu 1 skipped: idling at default_idle+0x23/0x40
[ 5497.727452] rcu: rcu_preempt kthread starved for 15723 jiffies! g160085 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[ 5497.758981] rcu: RCU grace-period kthread stack dump:
[ 5497.758981] rcu_preempt I14680 10 2 0x80004000
[ 5497.758981] Call Trace:
[ 5497.758981] __schedule+0x3f4/0x6f0
[ 5497.758981] schedule+0x81/0xb0
[ 5497.758981] schedule_timeout+0xb5/0x150
[ 5497.758981] ? __prandom_timer+0x8/0x8
[ 5497.758981] rcu_gp_kthread+0x69d/0xe70
[ 5497.758981] ? usb_stor_control_thread+0x8/0x8
[ 5497.758981] kthread+0x180/0x190
[ 5497.758981] ? usb_stor_control_thread+0x8/0x8
[ 5497.758981] ? change_clocksource+0x8/0x8
[ 5497.758981] ret_from_fork+0x35/0x40
[ 5518.810673] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 5518.814623] rcu: 1-...!: (0 ticks this GP) idle=048/0/0x0 softirq=62892/62892 fqs=0 last_accelerate: e014/e884, Nonlazy posted: ..D
[ 5518.814623] (detected by 3, t=5257 jiffies, g=160089, q=10499)
[ 5518.827577] Sending NMI from CPU 3 to CPUs 1:
[ 5518.834136] NMI backtrace for cpu 1 skipped: idling at default_idle+0x23/0x40
hs...@google.com <hs...@google.com> #56
ar...@gabrys.it <ar...@gabrys.it> #57
Hi, when there will be an update of the Android Studio? I have a problem with W11 + Ryzen + WSL2
I cant make this fix to work. I've installed newest Android Studio and copied/overrided files from #48 to:
C:\Users\username\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64
When I go to Android Studio -> SDK Managera -> SDK Tools and try to install Android Emulator Hypervisor Driver for AMD Processors I get the same error:
[SC] ControlService FAILED 1062:
Us�uga nie zosta�a uruchomiona.
[SC] DeleteService SUCCESS
[SC] StartService FAILED with error 4294967201.
Android Emulator Hypervisor Driver for AMD Processors installation failed. To install Android Emulator Hypervisor Driver for AMD Processors follow the instructions found at: https://github.com/google/android-emulator-hypervisor-driver-for-amd-processors
Done```
ya...@hebei.dev <ya...@hebei.dev> #58
ro...@animeindependent.net <ro...@animeindependent.net> #59
an...@gmail.com <an...@gmail.com> #60
hs...@google.com <hs...@google.com> #61
da...@gmail.com <da...@gmail.com> #62
Didn't work for me.
ad...@gmail.com <ad...@gmail.com> #63
ze...@gmail.com <ze...@gmail.com> #64
hs...@google.com <hs...@google.com> #65
ze...@gmail.com <ze...@gmail.com> #66
bi...@gmail.com <bi...@gmail.com> #67
on...@gmail.com <on...@gmail.com> #68
gd...@gmail.com <gd...@gmail.com> #69
ma...@gmail.com <ma...@gmail.com> #70
bp...@gmail.com <bp...@gmail.com> #71
Data:
1) Windows 11, Intel CPU, with WSL 2 installed and working (Hyper-V)
2) Tried Android emulator-31-3-14 and it runs slow (no acceleration)
3) Run command "emulator-check.exe accel" and the result is:
accel:
0
Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.22621) is installed and usable.
accel
4) Renamed the folder
FROM: C:\Program Files (x86)\Android\android-sdk\emulator
TO: C:\Program Files (x86)\Android\android-sdk\emulator.ORIG-31-3-14
5) Downloaded the Windows.ZIP from message #48 above, unziped into the folder:
C:\Program Files (x86)\Android\android-sdk\emulator
6) Reboot
7) Run command: "emulator-check.exe accel" and the result is unchanged:
C:\Program Files (x86)\Android\android-sdk\emulator>emulator-check.exe accel
accel:
0
Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.22621) is installed and usable.
accel
I've tried many things, but the result is the same. I'm out of ideas. By the lack of posts, I suspect that it is working for everyone else in the current version. Why not on my system?
-B
hs...@google.com <hs...@google.com> #72
"Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot." --------- This sentence comes from old days when only Intel HAXM is supported.
Nowadays, WHPX+HyperV may be a little bit slower than Intel HAXM but should not differ too much.
So the problem is why emulator runs slow. Can you tell me your CPU model?
And run "emulator" with "-verbose -show-kernel" options and paste the command line output?
Description
AI-203.7717.56.2031.7678000, JRE 11.0.10+0-b96-7249189x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 2400.0x1350.0
AS: Arctic Fox | 2020.3.1 Patch 2; Kotlin plugin: 203-1.5.31-release-550-AS7717.8; Android Gradle Plugin: (plugin information not found); Gradle: (gradle version information not found); Gradle JDK: version 11.0.10; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)Source: user_sentiment_feedback
IMPORTANT: Please read