It's too laggy

[akhnati]

The flag and the page it self is toog laggy, the flag does wave, but it doesn't look good, the "all options" menu takes a while to open.

This problem has been going on for 2 months; i'm currently using Windows 10, and the problem is problem this problem is only happening to me.

[krikienoid]

What browser are you using?
Are you using your own images in the flagwaver?
Can you open your developer console and see if there are any errors or warnings popping up?
This kind of stuff is difficult to troubleshoot without a lot of details to go off of

[akhnati]

I am using Google Chrome,
The page opens up already laggy,
And i can open the developer control but no warnings appear.

[krikienoid]

That's really strange! Again, I don't really know what's going on as I don't see any issues on my end, but any more info you can provide would help.

1. Are you able to go into the Performance tab of the dev tools, record about 10 seconds or so (but make sure the page is finished loading first), and send me the Profile?

2. Can you also visit the test page and see if it is any better?

3. Can you provide screenshots of 1 and 2?

[KyLeggiero]

It's probably a hardware problem. It's not exactly the smoothest on my 5-year-old MacBook Pro; I can imagine it'd be very intense for old or low-end machines

[krikienoid]

I agree that's probably likely, but I'd still like to see more detailed information to see if there's something that can actually be done about it.

Did you see any difference between the test page and the current live version? This would determine if we had a regression and would help pin-point the issue to a specific code change. Other than that though, I would have no idea where else to look.

[KyLeggiero]

@krikienoid sorry; I don't think I'll have time to test that out. I can make a note to check back in awhile to tell you if the now-in-test-but-will-then-have-been-the-live-version works the same or not; currently it just barely achieves full FPS for me.

[KyLeggiero]

Turns out I found some time! So I tested the live version, the test page you linked, and the version on master as cloned onto and running from my machine. Here's my results!

---

Here's how the live version performs for me:

Here's how the test page performs for me:

Here's how the current version on master performs for me:

---

Seems whatever performance enhancements you made for the test version really worked out 😁

[krikienoid]

Thanks for the confirmation! Unfortunately, the test version isn't an enhanced version, it's just reverting back to a really old version. Now the hard part is finding out which commit(s) caused the performance drop.

[KyLeggiero]

Best of luck, @krikienoid! I'm facing the same problem at work lol

[LugiKOOLAIDGamer]

I have the same problem, It's very laggy

[krikienoid]

I've done some tests using the Chrome dev tools Performance tab. I've tried throttling the CPU 6x and comparing Profiles, however, I do not see any noticeable difference. On my machine, both sites run smoothly at 60fps. I've also tried making the main loop function run multiple times per frame, but I was not able to get the latest FlagWaver to perform worse comparatively.

So I think I'll need help from someone with an old computer to pinpoint this issue. If anyone has an old computer, can you test the following links and see which ones perform better/worse?

https://krikienoid.github.io/flagwavertest/tests/v1.0.0/
https://krikienoid.github.io/flagwavertest/tests/2499b32/
https://krikienoid.github.io/flagwavertest/tests/7c4925f/
https://krikienoid.github.io/flagwavertest/tests/af299bd/

[krikienoid]

It's been over a year of no activity so I am closing this. If anyone still having issues wants to reopen this, please provide actionable information, such as identifying a specific commit or piece of code that is causing problems, or proposing a fix.