Skip to content

Remove memory_allocation_sub_allocation.png #346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
spencer-lunarg merged 1 commit into from
Sep 18, 2025
Merged

Remove memory_allocation_sub_allocation.png #346

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file removed chapters/images/memory_allocation_sub_allocation.png
View file
Open in desktop
Binary file not shown.
2 changes: 0 additions & 2 deletions chapters/memory_allocation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,6 @@ It is also worth noting that managing memory is not easy and developers might wa

Sub-allocation is considered to be a first-class approach when working in Vulkan. It is also important to realize there is a link:https://docs.vulkan.org/spec/latest/chapters/limits.html#limits-maxMemoryAllocationCount[maxMemoryAllocationCount] which creates a limit to the number of simultaneously active allocations an application can use at once. Memory allocation and deallocation at the OS/driver level is likely to be really slow which is another reason for sub-allocation. A Vulkan app should aim to create large allocations and then manage them itself.

image::{images}memory_allocation_sub_allocation.png[memory_allocation_sub_allocation.png]

== Transfer

The link:https://docs.vulkan.org/spec/latest/chapters/devsandqueues.html#VkPhysicalDeviceType[VkPhysicalDeviceType] advertises two main different types of GPUs, discrete and integrated (also referred to as UMA (unified memory architecture)). It is important for performance to understand the difference between the two.
Expand Down
2 changes: 0 additions & 2 deletions lang/jp/chapters/memory_allocation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,6 @@ Vulkan のメモリ管理に関する2つの Khronos のプレゼンテーショ

サブ割り当ては Vulkan では最も良いアプローチです。また、アプリケーションが同時に使用できるアクティブな割り当て数である link:https://docs.vulkan.org/spec/latest/chapters/limits.html#limits-maxMemoryAllocationCount[maxMemoryAllocationCount] が存在することも重要です。OS やドライバレベルでのメモリ割り当てと解放は非常に遅くなる可能性があり、これがサブ割り当てのもう一つの理由です。Vulkan アプリは大きな割り当てを作成し、それを自分で管理することを目指すべきです。

image::../../../chapters/images/memory_allocation_sub_allocation.png[memory_allocation_sub_allocation.png]

== 転送

link:https://docs.vulkan.org/spec/latest/chapters/devsandqueues.html#VkPhysicalDeviceType[VkPhysicalDeviceType] では、主にディスクリートと統合型（UMA（ユニファイド・メモリ・アーキテクチャ）とも呼ばれる）の2タイプの GPU を示しています。この2つの違いを理解することは、パフォーマンスにとって重要です。
Expand Down
2 changes: 0 additions & 2 deletions lang/kor/chapters/memory_allocation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,6 @@ Vulkan 메모리 관리에 관한 2개의 크로노스 프레젠테이션, link:

서브 할당은 Vulkan에서 작업할 때 가장 좋은 접근 방식입니다. 또한 애플리케이션이 한 번에 사용할 수 있는 동시 활성 할당 수에 제한을 두는 link:https://docs.vulkan.org/spec/latest/chapters/limits.html#limits-maxMemoryAllocationCount[maxMemoryAllocationCount]가 있다는 점도 중요합니다. OS나 드라이버 수준에서의 메모리 할당과 해제는 매우 느릴 수 있으며, 이것이 서브 할당의 또 다른 이유입니다. Vulkan 앱은 큰 할당을 생성한 다음 자체적으로 관리하는 것을 목표로 해야 합니다.

image::../../../chapters/images/memory_allocation_sub_allocation.png[memory_allocation_sub_allocation.png]

== 전송

link:https://docs.vulkan.org/spec/latest/chapters/devsandqueues.html#VkPhysicalDeviceType[VkPhysicalDeviceType]은 외장형과 통합형(UMA(통합 메모리 아키텍처, Unified Memory Architecture)라고도 함)의 두 가지 주요 GPU 유형을 나타냅니다. 이 둘의 차이점을 이해하는 것이 성능에 중요합니다.
Expand Down