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

Windows ISPC *For Consideration* #5166

Merged
merged 7 commits into from
Jan 30, 2025
Merged

Conversation

derwin12
Copy link
Collaborator

For discussions only .. This is my local code for running ispc - nothing special.

removed the #ifndef WXMSW and the updated the vs2022 project files.

One thing is ispc compiled for what?
ispc.exe "%(FullPath)" -o "$(IntDir)%(Filename).obj" --target=host

This compiles based on my PC's capabilities - do we need to set that to a value that is our now new low-bar for cpu requirements.
What was used on the mac size?

@dkulp
Copy link
Member

dkulp commented Jan 28, 2025

Most likely you want to use "--target=avx2-i32x16 --target=avx1-i32x16 --target=sse4.2-i32x8 --target=sse2-i32x8 --arch=x86_64" which is what is being used for Linux.. It compiles in all four and at runtime will select the one most appropriate based on the cpu.

@computergeek1507
Copy link
Member

can you pull in my workflow change and to see if it builds on github

@derwin12
Copy link
Collaborator Author

I think I did what you asked ..
Can I run a build/installer script on my machine? Is that msw\build_VS_x64.cmd ?
Would that create a zip I can pass to others to test?

@derwin12
Copy link
Collaborator Author

Simple tests .. 5secs off of 60s render.

@computergeek1507
Copy link
Member

You didn't merge in the GitHub action change to see if it compiles in github

@derwin12
Copy link
Collaborator Author

This latest push - I didnt have the HASISPC defined - I had it blocked out so it only did one file with ISPC.
I think it is in there .. I see the build ispc working..
image
Lets see the results of this next one. When I do release on my side now I am seeing upwards of 25-30% speed up.

@computergeek1507
Copy link
Member

computergeek1507 commented Jan 29, 2025

If it builds why not remove the the special "-ISPC" modifier and merge it, I can add the install code to the release and nightly action. If it works ship it.

@computergeek1507
Copy link
Member

in a couple sequences I tried it decreased render time by 25%ish

@derwin12
Copy link
Collaborator Author

Nervous .. lol. It is 30% faster in these test I have been doing. I know there is one big bug with ISPC reported last night.
Lets test for a couple days but it should work. Not sure what Dan wants to do with the #ifdef stuff - just remove it??
image

@computergeek1507
Copy link
Member

YOLO it, like the kids say

@cybercop23
Copy link
Collaborator

Can the layering bug be affecting the performance here? If it doesn't process layers, it will be faster. I see your PR is compiled, I'll download and test it this afternoon.

@derwin12 derwin12 changed the title Windows ISPC *DO NOT MERGE* Windows ISPC *For Consideration* Jan 29, 2025
@derwin12
Copy link
Collaborator Author

Can the layering bug be affecting the performance here? If it doesn't process layers, it will be faster. I see your PR is compiled, I'll download and test it this afternoon.

Its only the 2 render styles .. but sure it might have some effect on the results.

@dkulp
Copy link
Member

dkulp commented Jan 29, 2025

I think the main thing left to update before merging is the README.windows.

@dkulp dkulp merged commit 3d0cafb into xLightsSequencer:master Jan 30, 2025
2 checks passed
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