infrastructure/blender-projects-platform
7
1
Issues 48 Projects 1 Activity

Buildbot: Install OptiX SDK 7.4 on Windows x64 and Linux workers #116

New Issue
Closed
opened 2024-08-06 15:41:30 +02:00 by Sergey Sharybin · 1 comment
Sergey Sharybin commented 2024-08-06 15:41:30 +02:00
Owner
Copy Link

In order to get some of the speedup in Cycles OptiX a newer SDK needs to be installed. It should be safe to install OptiX SDK 7.4, as it only increases driver requirement, but does not affect compatible hardware list.

What needs to be done:

  • Software needs to be pushed to the workers (it's already pre-downloaded to a shared location, makes it simpler for the devops to work, as it requires an NVidia Develeper account to download)
  • OptiX SDK 7.4 installed alongside with previous versions (the new SDK si only to be used by the current vdev and future release tracks)
  • bdr-devops-core needs to be updated for Linux, as the default path name on linux has changed (NVIDIA-OptiX-SDK-7.3.0-linux64 vs NVIDIA-OptiX-SDK-7.4.0-linux64-x86_64)
  • pipeline_config.yaml in Blender respository needs to be updated to 7.4.0

Ref #125899

In order to get some of the speedup in Cycles OptiX a newer SDK needs to be installed. It should be safe to install OptiX SDK 7.4, as it only increases driver requirement, but does not affect compatible hardware list. What needs to be done: - [x] Software needs to be pushed to the workers (it's already pre-downloaded to a shared location, makes it simpler for the devops to work, as it requires an NVidia Develeper account to download) - [x] OptiX SDK 7.4 installed alongside with previous versions (the new SDK si only to be used by the current vdev and future release tracks) - [x] bdr-devops-core needs to be updated for Linux, as the default path name on linux has changed (`NVIDIA-OptiX-SDK-7.3.0-linux64` vs `NVIDIA-OptiX-SDK-7.4.0-linux64-x86_64`) - [x] `pipeline_config.yaml` in Blender respository needs to be updated to 7.4.0 Ref #125899
Sergey Sharybin added the
Service
Buildbot
 label 2024-08-06 15:41:30 +02:00
Bart van der Braak added the
Type
Deployment
 label 2024-08-06 17:37:02 +02:00
Bart van der Braak self-assigned this 2024-08-06 17:37:12 +02:00
Bart van der Braak added this to the DevOps Progress Board project 2024-08-06 17:37:17 +02:00
Sergey Sharybin commented 2024-09-23 14:40:31 +02:00
Author
Owner
Copy Link

This has been done in blender/blender@4f5b6b114d

This has been done in blender/blender@4f5b6b114d7
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Service
Buildbot
builder.blender.org

  
Service
Chat
chat.blender.org

  
Service
Gitea
projects.blender.org

  
Service
Translate
translate.blender.org

  
Type
Bug
Errors or incorrect behaviour

  
Type
Config
Configuration change

  
Type
Deployment
Version deployment or rollback

  
Type
Feature
New functionality or enhancement

  
Type
Setup
New service setup and deployment

No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
DevOps Progress Board
Assignees
Clear assignees
No Assignees
Bart van der Braak
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-projects-platform#116
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?