Performance tips & tricks from a Unity consultant | Unite 2024

Поділитися
Вставка
  • Опубліковано 29 лис 2024

КОМЕНТАРІ • 8

  • @alekseyrastegaev3077
    @alekseyrastegaev3077 Місяць тому +4

    Nice! Need more videos like this from unity, also with much more deep explanation / examples / techniques.

  • @AntonovDVRUS
    @AntonovDVRUS Місяць тому +8

    0:00 Intro
    1:50 Profiling hotspots
    3:38 Unity's CPU profiler module
    5:13 Native profiler
    7:30 Superluminal
    10:28 Shader compilation spikes
    11:42 Shader prewarming
    13:10 Shader variant collection
    14:46 Batching
    17:53 RenderMeshInstanced API in action
    19:40 Multiple cameras
    21:46 New graphics features
    22:54 GPU bound
    24:09 Overdraw
    25:22 RenderDoc
    27:07 Quad overdraw
    28:18 Shader performance
    31:31 Untracked memory
    35:44 Reserved managed memory
    40:52 Full call stack of a GC.Alloc call
    42:12 Asset duplication
    44:17 Asset duplication - Tools
    45:47 Unity Data Tools
    46:53 Shader memory
    48:52 In summary

    • @bots_op
      @bots_op Місяць тому

      you are a hero

  • @크리엘-k9o
    @크리엘-k9o Місяць тому +6

    Thank you for this session!

  • @niklasmikkelsen4701
    @niklasmikkelsen4701 Місяць тому +3

    This is unexpectedly good 🎉

  • @JoeCoo7
    @JoeCoo7 Місяць тому +4

    Great Talk! Thanks.

  • @glock6554
    @glock6554 Місяць тому +1

    Keep it coming Unity!

  • @mitaywalle
    @mitaywalle Місяць тому

    great talk.
    1. Auditor should be mensioned in offical manual about shader prewarming in android subcategory
    2. more info abount Untracked memory from native profilers stacktraces is very important and usefull
    3. new Shader chunk loading need more details in manual page about drawback mesnioned in video (about low chunk -> slower compilation, cause by disk load)
    4. using native collections in main-thread should be on slide
    5. memory fragmentation need more built in profiling tools, or more info in manual, if they're there already. We can't understand, is memory fragmented or not. Or is it reason for memory crash or not