# WGLMakie in Pluto firefox overuse of CPU resources

**URL:** https://discourse.julialang.org/t/wglmakie-in-pluto-firefox-overuse-of-cpu-resources/95494
**Category:** Performance
**Tags:** pluto, makie, wglmakie
**Created:** [March 3, 2023, 12:40pm UTC](https://discourse.julialang.org/t/wglmakie-in-pluto-firefox-overuse-of-cpu-resources/95494 "2023-03-03T12:40:44Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![filchristou](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/filchristou/32/26760_2.png) [@filchristou](https://discourse.julialang.org/u/filchristou)
#### Post date: [March 3, 2023, 12:40pm UTC](https://discourse.julialang.org/t/wglmakie-in-pluto-firefox-overuse-of-cpu-resources/95494/1 "2023-03-03T12:40:44Z")

</div>

I am using WGLMakie to make some interactive plots in Pluto.  
After making some, my % CPU resources spike like following:  
_starting with no WGLMakie figure and ca. 30% CPU usage_  
_1 figure ca. 150 % CPU usage_  
_2 figure ca. 175 % CPU usage_  
_3 figure ca. 370 % CPU usage_  
_4 figure ca. 400 % CPU usage_  
_5 figure ca. 430 % CPU usage_  
_6 figure ca. 460 % CPU usage_  
_7 figure ca. 500 % CPU usage_

The measurements are after the figures are made and essentially the notebook is idle.  
If I switch tab/application my % CPU resources drop to normal ca. 30% CPU.  
If I switch back to the notebook and without doing anything I get again 500 % CPU usage.

**The CPU usage comes from the browser client**  
I also tried with a remote server.  
The remote server doing all the hard visualization work has NO overuse of CPU resources  
However my browser client locally still gets 500% CPU.  
So it’s a browser client thing.

# Reproducibility

Just open a Pluto notebook and do `using WGLMakie` and a series of `scatter(1:10)`

 ![image](https://global.discourse-cdn.com/julialang/original/3X/a/6/a6b2a0c33282af5b4c2894dc6d30502e2ab6014e.png)

> **System settings**
>
> #### Julia `versioninfo()`
> 
> Julia Version 1.8.4  
> Commit 00177ebc4fc (2022-12-23 21:32 UTC)  
> Platform Info:  
> OS: Linux (x86\_64-linux-gnu)  
> CPU: 12 × 12th Gen Intel(R) Core™ i5-1235U  
> WORD\_SIZE: 64  
> LIBM: libopenlibm  
> LLVM: libLLVM-13.0.1 (ORCJIT, goldmont)  
> Threads: 1 on 12 virtual cores
> 
> #### Packages
> 
> Pluto v0.19.19  
> WGLMakie v0.8.6
> 
> #### OS
> 
> Debian 11
> 
> #### Browser
> 
> Firefox 102.8.0esr (64-bit)

---

<div class="post-metadata">

### Author: ![ederag](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ederag/32/4106_2.png) [@ederag](https://discourse.julialang.org/u/ederag)
#### Post date: [March 4, 2023, 9:09am UTC](https://discourse.julialang.org/t/wglmakie-in-pluto-firefox-overuse-of-cpu-resources/95494/2 "2023-03-04T09:09:15Z")

</div>

Cross-posted from [zulip](https://julialang.zulipchat.com/#narrow/stream/243342-pluto.2Ejl/topic/WGLMakie.20awfully.20slow).  
I was able to reproduce, but it happens we both have the same firefox version - `102.8.0esr (64-bit)`.