Is spawning additional threads a problem or is a “natural process”. Anyways when i run the rendering extension, my computer seems to overheat and slow down the sketchup model (moving around is difficult). It is taking me about 1 hour to render, while other users with more complex models obtain a high-res image under 15 min. Performance is poor. I just want to know if this could be a problem of sketchup (and its compatibility with the extension), my computer, or the extension itself.
Yes, i was actually rendering an image when i took the photo, sorry for not considering it. I still think that there’s something wrong with the extension. When i run it, my computer seems to overheat and slow down the sketchup model (moving around is difficult). It is taking me about 1 hour to render, while other users with more complex models obtain a high-res image under 15 min. Performance is poor. I just want to know if this could be a problem of sketchup (and its compatibility with the extension), my computer, or the extension itself.
When a programmer knows that a task can be split into independent parts, it is not unusual to write the code to spawn off separate threads. There is some extra complexity when doing so, but it reduces the total run time, often in proportion to the number of threads.
Unless you use the same renderer with the same settings on the same model, it isn’t possible to conclude much by comparing rendering times - except in one case: some renderers can use hardware acceleration in the graphics to speed rendering. This is common on Windows PCs that have Nvidia graphics. But the capabilities they need weren’t added to Apple Silicon until the M3. So far as I know, no renderer has been released yet that fully exploits the M3 and it wouldn’t benefit your pre-M3 Mac in any case.
uuuuuuuh it’s fine then 
I mean, it’s still high, but not an anomaly.
Softwares are like goldfishes, the bigger the bowl, the bigger the fish.
say you have 12 cores in your CPU, sketchup making a rendering of a very complex model filled with faces taking 10 cores is not an anomaly.
If I were to make the same task on my computer (8 cores), I would probably go up to 600+%
off course, you’re asking a sketchup extension to make a high demanding task, and at the same time, you try to move around in your big model. don’t do that !
when you render, let it render. don’t touch sketchup, if you can, don’t touch anything, close what’s not needed (music, browser…) and let it work alone.
also, plug-in your mac. rendering takes a lot of energy, and it can quickly empty your battery, making it hotter.
as slbaumgartner said, are they rendering the exact same model as you, with the exact same parameters, and the exact same machine ?
The things Dave pointed out in the beginning will matter when rendering.
You have a vine hanging in your model. it’s made of many tiny leaves, they are small faces. Well the renderer needs to simulate light bouncing on each and every leave.
try rendering without the vegetation, and you’ll see a difference.
the other thing is image size :
if rendering a 1000x1000px image takes you 10 minutes, then a 2000x2000pixel image will take 40min.
it’s basic maths.
So maybe your colleagues have fewer plants, or have simpler geometry, and maybe they are making smaller images, and maybe they have a dedicated GPU (nvidia) that works well with their rendering tool.
Las Mac de las series M son increíbles, pero 16 gb se van a quedar pequeños de para 3D, de esos 16 más de 2gb ocupa el sistema operativo, si vas a renderizar es posible que te quedes sin memoria y el sistema empieza a usar la memoria del SSD lo que se llama swap memory, el problema con eso es que la memoria SSD es bastante más lenta que la memoria ram, y vas a tener una caída de rendimiento considerable, igual para todas tareas que utilicen bastante cpu, como animaciones o simulaciones con clothworks por ejemplo o en otro software.