summary refs log tree commit diff stats
path: root/results/scraper/box64/2152
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-16 14:55:48 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-16 14:55:48 +0200
commit63d2e9d409831aa8582787234cae4741847504b7 (patch)
tree595fae753d2eb293437226eaab2eed208463f132 /results/scraper/box64/2152
parent2843bb65aeaeb86eb89bf3d9690db61b9dc6306e (diff)
downloadqemu-analysis-box64.tar.gz
qemu-analysis-box64.zip
add box64 bug reports box64
Diffstat (limited to 'results/scraper/box64/2152')
-rw-r--r--results/scraper/box64/215210
1 files changed, 10 insertions, 0 deletions
diff --git a/results/scraper/box64/2152 b/results/scraper/box64/2152
new file mode 100644
index 000000000..a88aa79f4
--- /dev/null
+++ b/results/scraper/box64/2152
@@ -0,0 +1,10 @@
+Very notable performance due to Build and Release Box64 #4772: Commit 5bde45c  (Winlator)
+When 0.3.2 was released I tried it and I noticed an big performance regression on winlator (android).

+

+I tried diffefent 'box64-latest.wcp' builds from the actions tab to identify which build was the one that introduced the regression till I found it:

+

+From [this build](https://github.com/ptitSeb/box64/actions/runs/12137674194) (related to commit https://github.com/ptitSeb/box64/commit/5bde45cc8695e85de56dc11ecc391bfb2b74bb38) the performance regression in some games is massive. As it can be seen in the video the FPS drop like crazy going down to even 13fps only: https://streamable.com/h9qfy7

+

+With the build 4771 from the same actions tab (and previous builds) it's quitte stable and the FPS can vary from 27 to 32 in the same area but it's not as bad as it's on #4772 and next ones.

+

+I'm hoping the performance regression can be reversed so we, winlator users, can enjoy the other improvements and fixed that I suppose were added to 0.3.2
\ No newline at end of file