lime icon indicating copy to clipboard operation
lime copied to clipboard

Lime 8.2.0 runs worse than 8.1.3

Open Vortex2Oblivion opened this issue 1 year ago • 11 comments

After upgrading Lime to 8.2.0 I noticed that it was running worse than on 8.1.3

After doing a bit of testing on the OpenFL bunny mark demo it seems to run worse This is on lime 8.1.3 with 9.4.0 and git hxcpp image image

After upgrading Lime to 8.2.0 and keeping OpenFL and hxcpp on the same versions I tried it again image image

The CPU usage is almost DOUBLED and the memory also increased as well.

More testing should probably be done as I havent tried on other targets yet.

Vortex2Oblivion avatar Oct 22 '24 23:10 Vortex2Oblivion

I confirm that this is a possible problem. I ran back-to-back tests with my bunny mark and noticed large FPS variations, namely an 84-60 drop off, which is not huge given my processor's speed. These only occurred on 8.2.0, and openfl versions did not seem to affect this number; using 9.4.0 or 9.2.2 did not appear to change performance. HL performs poorly, making the problem noticeable. from drop-offs of around 80 FPS.

RapperGF avatar Oct 22 '24 23:10 RapperGF

I have ran a bunny mark sample in openfl with both lime 8.1.3 and 8.2.0 but I'm not getting the observed symptoms. Though that may be because I have a beefy computer.

Sword352 avatar Oct 23 '24 07:10 Sword352

runs fine for me even though my pc is 16 year old-ish

lime 8.1.3 and openfl 9.3.4 image

lime 8.2.0 and openfl 9.4.0 image

pc specs CPU: Intel(R) Xeon(R) CPU X5690 @ 3.47GHz GPU: AMD Radeon RX 550 Memory: 8 GB Motherboard: ASUSTeK Computer INC. P6T SE Rev 1.xx

picnicpip avatar Oct 23 '24 07:10 picnicpip

runs fine for me even though my pc is 16 year old-ish

lime 8.1.3 and openfl 9.3.4

image

lime 8.2.0 and openfl 9.4.0

image

pc specs

CPU: Intel(R) Xeon(R) CPU X5690 @ 3.47GHz

GPU: AMD Radeon RX 550

Memory: 8 GB

Motherboard: ASUSTeK Computer INC. P6T SE Rev 1.xx

Keep in mind I was testing with 200k bunnies It wasn't noticeable at first

Vortex2Oblivion avatar Oct 23 '24 10:10 Vortex2Oblivion

Testing with the BunnyMark from lime-samples and openfl-samples didn't appear to have any difference on the Lime version used.

openfl-samples BunnyMark - 200k bunnies
OpenFL 9.4.0 + Lime 8.1.3
8 1 3-openfl9 4 0
OpenFL 9.4.0 + Lime 8.2.0
8 2 0-openfl9 4 0

Except for the high GPU usage (which is expected from an iGPU) CPU and memory usage were roughly the same. If it's worth mentioning I compiled to C++ target on Release, using git hxcpp 4.3.68

NotHyper-474 avatar Oct 23 '24 17:10 NotHyper-474

Testing with the BunnyMark from lime-samples and openfl-samples didn't appear to have any difference on the Lime version used.

| openfl-samples BunnyMark - 200k bunnies |

|--------|

| OpenFL 9.4.0 + Lime 8.1.3 |

| 8 1 3-openfl9 4 0 |

| OpenFL 9.4.0 + Lime 8.2.0 |

| 8 2 0-openfl9 4 0 |

Except for the high GPU usage (which is expected from an iGPU) CPU and memory usage were roughly the same.

If it's worth mentioning I compiled to C++ target on Release, using git hxcpp 4.3.68

Very interesting since I've seen people report it running worse and people report that it is running about the same. May I ask what your pc specs are?

Vortex2Oblivion avatar Oct 23 '24 17:10 Vortex2Oblivion

Very interesting since I've seen people report it running worse and people report that it is running about the same. May I ask what your pc specs are?

AMD Ryzen 5 4600G, 16 GB DDR4 at 3000 MHz, MSI A520M-A Pro mobo, just a mid-range PC

NotHyper-474 avatar Oct 23 '24 17:10 NotHyper-474

Is it possible it only runs bad on certain hardware? I have a ryzen cpu and a nvidia gpu.

Vortex2Oblivion avatar Oct 23 '24 19:10 Vortex2Oblivion

The problem seems to persist on lime 8.2.1

Vortex2Oblivion avatar Nov 03 '24 15:11 Vortex2Oblivion

on develop (abb92a2a849a7ae18d5112fa647e4e6e6f28919d) and OpenFL 9.4.1 seems fine on my laptop

Image

Specs: CPU: 12th Gen Intel(R) Core(TM) i5-12450H GPU: Intel UHD Graphics

ghost avatar Jan 18 '25 12:01 ghost

Perhaps something else changed in the initial test?

For example, are we talking about Lime 8.1 and 8.2 on Haxelib, or are these compiled from source? If compiled from source, which compiler, and which processor architecture? We could be seeing differences in Visual Studio versions, or X86 compared to X64 for example.

If the Lime main loop was changed, a bad main loop can also have this drastic of a change.

Oh, one more thought would be DPI scaling, or monitor refresh rate. I forget what changed in Lime 8.2, though if either of those features were better supported, those could have an impact.

jgranick avatar Jan 20 '25 17:01 jgranick