# Performance Difference: MacOS VS Windows

**URL:** <https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378>\
**Category:** Questions\
**Created:** [April 5, 2019, 1:42pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378 "2019-04-05T13:42:06Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 5, 2019, 1:42pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/1 "2019-04-05T13:42:06Z")

</div>

Hi,  
we are currently working on a project and noticed some huge performance differences between Desktop PC and Mac.We tried to reproduce the issue in the following playground project: [https://www.babylonjs-playground.com/#CHQ4T#144](https://www.babylonjs-playground.com/#CHQ4T#144)

Here’s what’s happening:  
Windows 10 Desktop PC / Google Chrome:

- 60 FPS constant
- Controls are smooth
- Video is playing fine

Microsoft Surface Windows 10 / Google Chrome:

- 30 FPS constant
- Controls are smooth
- Video is playing fine

MacBook Pro MacOS 10.14 / Safari:

- lerping between 60 FPS and 32 FPS every second (?) constantly
- Video speed is lerping and it seems very stuttering
- controls are stuttering the same way as the video

MacBook Pro MacOS 10.14 / Google Chrome:

- constant 15 FPS
- Video runs little stuttering but constantly at 15 FPS
- controls are the same

So we only have stuttering problems on the MacBook Pro. I know we are using a lot of Polygons (this is only for testing reasons). But on Windows devices it is working all fine. Maybe someone knows how we can fix our Mac problems, to get it running as smooth as on Windows.

Best regards,

Lennart

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 5, 2019, 2:14pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/2 "2019-04-05T14:14:13Z")

</div>

I have no Mac but @sebavan will be able to give it a try (probably not before next week. Thanks a lot for your patience)

In the meantime, can you do a profile on your Mac and post the results here?

---

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 5, 2019, 2:56pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/3 "2019-04-05T14:56:14Z")

</div>

Hi @Deltakosh ,  
thanks for the fast reply. Funny thing is: if i open the console in Safari the framerate is constantly at 47 FPS. As soon as i close it, it’s again lerping between 60 and 32 FPS. If I open again, it’s again on 47 FPS constantly, and so on.

So I don’t know how to send you a meaningful timeline.

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 5, 2019, 4:45pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/4 "2019-04-05T16:45:48Z")

</div>

And do you see anything in the profiler?

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 5, 2019, 5:28pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/5 "2019-04-05T17:28:50Z")

</div>

Also can you use another video from a faster server?  
Maybe it is related to the video

---

<div class="post-metadata">

**Author:** ![nasimiasl](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/nasimiasl/32/34_2.png) [@nasimiasl](https://forum.babylonjs.com/u/nasimiasl)\
**Post date:** [April 5, 2019, 5:34pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/6 "2019-04-05T17:34:23Z")

</div>

i see that different on mac ( safari vs chrome too)

---

<div class="post-metadata">

**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\
**Post date:** [April 6, 2019, 12:33am UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/7 "2019-04-06T00:33:48Z")

</div>

It is not related to video or VAO but the number of triangles only: [https://www.babylonjs-playground.com/#CHQ4T#149](https://www.babylonjs-playground.com/#CHQ4T#149) -\> no textures  
[https://www.babylonjs-playground.com/#CHQ4T#151](https://www.babylonjs-playground.com/#CHQ4T#151) -\> no VAO

We have on this very scene simply on the mesh : 12 696 000 vertices and it looks like the angle backend is having trouble to deal with it on a mac.

You should file a bug on chromium, I tried a couple of workaround without any success.

---

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 7, 2019, 6:01pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/8 "2019-04-07T18:01:54Z")

</div>

We already played the Same Video from different Servers and also different Videos with different Codecs and There is no difference at all.  
The video Speed/Performance seems to be only affected by the FPS of the whole scene.

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 8, 2019, 2:30pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/9 "2019-04-08T14:30:04Z")

</div>

Ok and did you try to reduce the complexity of the sphere as @sebavan mentioned?

---

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 8, 2019, 2:35pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/10 "2019-04-08T14:35:08Z")

</div>

We know, that we can reduce the polycount and it will somehow result in a better performance, but still not as good as on Windows. The sphere is just an example to show our problem. We are using meshes with 1 Mio or way lower polys in our scene and there still is this difference between Mac and Windows. It even runs better on Windows devices which are less powerful than the MacBook Pro.

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 8, 2019, 2:37pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/11 "2019-04-08T14:37:49Z")

</div>

Ok so if you need that polycount then you need to open a bug on chrome database. This is definitely an implementation issue on their backend

---

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 8, 2019, 2:52pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/12 "2019-04-08T14:52:01Z")

</div>

But why is it running perfectly at 60 FPS constantly in Chrome on Windows then? We only have problems on Mac, in Chrome and Safari as well, so it can’t only be a Chrome bug. Any suggestions?

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 8, 2019, 2:55pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/13 "2019-04-08T14:55:23Z")

</div>

it is a problem on Chrome for Mac (not the same as Chrome for Windows: different code is used)

---

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 8, 2019, 3:01pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/14 "2019-04-08T15:01:34Z")

</div>

I’m sorry but I think we’re talking past each other. So if it’s a Chrome problem, why do we face the same issue on Safari too ?

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 8, 2019, 3:05pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/15 "2019-04-08T15:05:45Z")

</div>

Because they are both initially based on the same webkit engine. Or they are both using some MacOS feature that we don’t know about

One thing is sure: it is not on JavaScript side

---

<div class="post-metadata">

**Author:** ![CLB\_ZReality](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/clb_zreality/32/4293_2.png) [@CLB\_ZReality](https://forum.babylonjs.com/u/CLB_ZReality)\
**Post date:** [April 8, 2019, 3:09pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/16 "2019-04-08T15:09:39Z")

</div>

Alright. Thank you for your efforts. We will look into this and keep you posted.

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [April 8, 2019, 3:14pm UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/17 "2019-04-08T15:14:19Z")

</div>

please share your bug report here so we can upvote it

---

<div class="post-metadata">

**Author:** ![withADoveInOneHand](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/withadoveinonehand/32/1243_2.png) [@withADoveInOneHand](https://forum.babylonjs.com/u/withADoveInOneHand)\
**Post date:** [April 9, 2019, 12:41am UTC](https://forum.babylonjs.com/t/performance-difference-macos-vs-windows/2378/18 "2019-04-09T00:41:36Z")

</div>

Intentionally impeding open web standards really is Apple’s best kept secret.
