Intro

What is Google Helper process

Can you disable Google Helper?

How to reduce CPU usage

Check your plugins and extensions

Check for CPU-consuming apps

Update the macOS

Declutter your desktop

Disable Google Chrome Helper renderer

Reset Chrome to default settings

Outro

Intro

Chrome is Eating my GPU

Disable Hardware Acceleration

Testing the fix

Reduce the amount of geometry in the scene

Close other programs

Reduce Texture Resolution

Get a GPU with more Vram

Summary

Tweak 2: Disable Chrome "Use Hardware Acceleration When Available"...

Tweak 3: Open chrome://flags

Enable the Override software rendering

Enable the "Override software rendering list"...

Close All Un-Used Tabs...

1. Eliminate render-blocking JavaScript and CSS

2. Prioritize visible content

Load scripts asynchronously

Client-side rendering

Server-side rendering

Identifying critical CSS

Loading the remaining, non-critical CSS

Render blocking CSS recommendations

Recommendations for instant mobile web apps

Intro

Fixed function lighting is gone

JavaScript performance

Declaring array size

Object storage

V8 garbage collector

Rendering

Rendering Loops

Input latency

WebGL inspector

Why should you as an app developer care about memory use?

How the low memory killer decides what to kill

Why keep previous and cached processes?

Memory sharing

Using PSS for app memory impact

Key takeaways

Application memory impact depends on device memory pressure

What about the rest of the memory?

Native allocations

Conclusion

Intro

Selecting an Element in the Browser

Inspecting element states

Computed Elements

Selecting Elements

Adding files to the Playground

XHR (XML HTTP Request)

Tracking cookies

Mailtag

Intro

Important Project Settings

Pathtracer Tips

Quixel Bridge is gone?

Lumen Tips

Reflection Options

New Lumen Reflection Options

Raytraced Reflections

Raytraced Translucency

Outro and Recommendations

Adhere to copyright laws

Different map areas have different resolution

Starting RenderDoc, and initializing the Injection

Injecting into the Process ID for the Google Chrome GPU process

What you see is what you will get

Beware of too big data captures

Evaluating the amount of data captured based on the file size of the capture

Make sure to release the injection

Importing the .rdc file

Processing times can be excruciatingly long

Reducing the number of material slots, by baking to one texture

Removing all material slots of the duplicate

Exporting the unwrapped mesh from MeshLab

Verifying the unwrapped UV map imported from MeshLab

Configuring settings for the texture baking process

Noticing erroneous results due to inadequate projection settings

Noticing erroneous results due to insufficient margin

Connecting the baked texture to the single material

Noticing erroneous results due to excessive Extrusion distance

Further decreasing the Extrusion distance and rebaking

Considerations to improve the resolution of the texture

Evaluating the result of the final baking settings

Testing the result by exporting the refined mesh as an OBJ

Creating a material to render the baked texture

Showcase of Benjamin Bardou's experiments

Learning how Ray Length settings can affect your render time

Discover the difference between global AO vs. Material based AO

Using AO Cache

How to render AO as a separate pass for compositing inside of After Effects

Baking AO into a texture & uses for game asset design

Adhere to copyright laws

Different map areas have different resolution

Starting RenderDoc, and initializing the Injection

Injecting into the Process ID for the Google Chrome GPU process

What you see is what you will get

Beware of too big data captures

Evaluating the amount of data captured based on the file size of the capture

Make sure to release the injection

Importing the .rdc file

Processing times can be excruciatingly long

Reducing the number of material slots, by baking to one texture

Removing all material slots of the duplicate

Exporting the unwrapped mesh from MeshLab

Verifying the unwrapped UV map imported from MeshLab

Configuring settings for the texture baking process

Noticing erroneous results due to inadequate projection settings

Noticing erroneous results due to insufficient margin

Connecting the baked texture to the single material

Noticing erroneous results due to excessive Extrusion distance

Further decreasing the Extrusion distance and rebaking

Considerations to improve the resolution of the texture

Evaluating the result of the final baking settings

Testing the result by exporting the refined mesh as an OBJ

Creating a material to render the baked texture

Showcase of Benjamin Bardou's experiments