Skip to content
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.

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

bp: Improve max sync object message #8470

Merged

Conversation

spencer-lunarg
Copy link
Contributor

for #8469

now prints

Validation Performance Warning: [ BestPractices-SyncObjects-HighNumberOfFences ] | MessageID = 0xa9f4ff68 | vkCreateFence(): [AMD] [NVIDIA] High number of VkFence objects created. 4 created, but recommanded max is 3. Minimize the amount of CPU-GPU synchronization that is used. Semaphores and fences have overhead. Each fence has a CPU and GPU cost with it.

@spencer-lunarg spencer-lunarg requested a review from a team as a code owner August 28, 2024 16:03
@ci-tester-lunarg
Copy link
Collaborator

CI Vulkan-ValidationLayers build queued with queue ID 245137.

@ci-tester-lunarg
Copy link
Collaborator

CI Vulkan-ValidationLayers build # 17338 running.

@ci-tester-lunarg
Copy link
Collaborator

CI Vulkan-ValidationLayers build # 17338 passed.

@spencer-lunarg spencer-lunarg merged commit d9ae959 into KhronosGroup:main Aug 28, 2024
21 checks passed
@spencer-lunarg spencer-lunarg deleted the spencer-lunarg-bp-sync branch August 28, 2024 17:00
@filnet
Copy link
Contributor

filnet commented Aug 28, 2024

There are similar limits checked for semaphores, barriers, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants