How to Update Metadata for Blender Benchmark to Support Windows ARM64

Hello Blender Development Team,

I have ported the Blender Benchmark to run on Windows ARM64. The code changes have been made, and I have tested the executable on a Windows ARM64 device.

However, I encountered an issue with the metadata used by Blender Benchmark. The current metadata does not include configurations for Windows ARM64, which prevents the benchmark from automatically downloading and integrating Blender for this architecture. To work around this, I had to manually download Blender ARM64 and place it in a specific path.

MetaDataURL- opendata.blender.org/benchmarks/metadata/

I would like to know how this metadata can be updated to include configurations for Windows ARM64? And How this metadata changes/update is maintained? This will enable Blender Benchmark to automatically download and integrate Blender for this architecture ARM64 and OS windows.

Could you please guide me on the process of metadata update or direct me to the appropriate person or resource?

Thank you for your assistance!

Regards,
Aamir

1 Like

Hi,

I believe it is best to add this question to the PR you submitted.

So it can be replied within context of the patch itself.

Regards,
Dalai

Hello, may I ask if the prerequisite for your submission is that you can already run blender on a computer based on ARM64 CPU and Windows operating system?
I am porting blender to an Android tablet and have some questions. Can you please help me?

You can find daily windows/arm builds over at Blender Builds - blender.org

The plan is to ship official support in blender 4.3 in November

Hi,

For the metadata an intuitive answer is: follow what is done for the macOS.

For the launcher itself the current PR needs work to keep it able to deliver universal binaries for macOS: there needs to be more clear separation between “default” architecture, and x64 one. But I also not sure how important it is, since the x64 launcher seems to work fine, and having two different launchers will make people confused anyway, and people will inevitably use x64 launcher on WoA.

Hi @sergey ,

Thank you for your feedback. These changes are intended to add support for Snapdragon X Elite Devices (Windows running on ARM64). While the x64 launcher works fine on Snapdragon X Elite ARM64 devices, it runs under emulation, not native on ARM64. To avoid this, I have ported the Benchmark to run natively on ARM64, and It works well with native Blender version for ARM64.

Regarding the metadata, you mentioned: “For the metadata an intuitive answer is: follow what is done for the macOS.” Could you please provide guidance on how to update this below metadata? I checked and found that the relevant file is not part of the Blender-Benchmark repo. Who maintains this metadata? If I need to update it, so any help on how I can access it would be appreciated.

https://opendata.blender.org/benchmarks/metadata/

Regards,
Aamir

The metadata you’re linking comes from the current production setup of OpenData. It does not have WoA builds in it, this is why you don’t see it.

The architecture is a part of a Blender build model: blender-open-data/metadata.py at main - blender-open-data - Blender Projects So in order for WoA builds to appear in the metadata JSON reported by the website the corresponding build needs to be added in the admin interface of the site.

The missing part is to make the launcher detect the proper (host) CPU and pick up proper Blender architecture to benchmark.

Hi @sergey ,

Thank you for the clarification. I understand now that the current metadata setup does not include WoA builds because they haven’t been added to the production setup yet.

Could you please guide me on how to proceed with adding the WoA builds to the admin interface of the site? Is there a specific process or person I should coordinate with to get this done? This is quite critical, and a call to discuss this would be really helpful. Please let me know if possible to have call.

Thanks again for your assistance.

Best regards,
Aamir

I am not sure why it is critical and bypassed communication with us. From our perspective it was not a priority, especially due to limited developers time (to either implement the feature now, or to on-board or guide new developer into the area). Please send us an e-mail so we can see and discuss details. Use both mine and Francesco’s emails: sergey AT blender.org and francesco AT blender.org.

Hi Sergey,

Thank you for your response. I understand the constraints and appreciate your time. This is to bring us on same page.

Based on your previous comments, I downloaded the x64 Blender-Benchmark launcher from the Blender OpenData website and the Blender daily build ARM64 version. I manually placed the ARM64 Blender in a specific path Because the current metadata does not include configurations for Windows ARM64 and it prevents the x64 benchmark launcher from automatically downloading and integrating Blender for this architecture. Therefore, I manually downloaded and placed the ARM64 Blender in a specific path.

After setting this up, I ran the x64 benchmark tool on WoA, and it was running successfully, and it provided the benchmark results on WoA same as the ARM64 Ported one. This indicates that the x64 Blender-Benchmark launcher can work with the ARM64 Blender, provided the metadata is updated to include WoA builds.

It seems that the only change needed is to update the metadata to support WoA builds. Could you please guide me on how to proceed with this? I will also send an email to you and Francesco to discuss the details further.

Thank you again for your assistance.

Best regards,
Aamir