64-bit timedemo results

[imw]

32-bit, Windows 11, no launch options
11615 frames 52.784 seconds 220.05 fps ( 4.54 ms/f) 31.663 fps variability

64-bit, Windows 11, no launch options
11615 frames 47.379 seconds 245.15 fps ( 4.08 ms/f) 36.173 fps variability

64-bit, Windows 11, -vulkan
11615 frames 47.297 seconds 245.58 fps ( 4.07 ms/f) 35.879 fps variability

edit: Star Trek is to blame.

[libadwaita (she/her)]

What are your system specs? I benchmarked Vulkan a few weeks ago when the GNU/Linux Vulkan beta first dropped I saw a fairly marginal improvement given my somewhat powerful CPU and older GPU.

I'm assuming your system is more well balanced than mine is.

[imw]

Originally posted by libadwaita (she/her):

What are your system specs? I benchmarked Vulkan a few weeks ago when the GNU/Linux Vulkan beta first dropped I saw a fairly marginal improvement given my somewhat powerful CPU and older GPU.

I'm assuming your system is more well balanced than mine is.

Ryzen 7 3700x
16 GB RAM
Nvidia 2070 Super
B550 mobo from ASUS

I did another round of testing, and ran each timedemo twice, keeping the second result. I thought that maybe various things needed to be pre-cached on the first try, and might explain explained less than stellar results on my first timedemo runs.

32-bit, Windows 11, no launch options
11615 frames 54.257 seconds 214.07 fps ( 4.67 ms/f) 25.523 fps variability

64-bit, Windows 11, no launch options
11615 frames 49.971 seconds 232.43 fps ( 4.30 ms/f) 32.727 fps variability

64-bit, Windows 11, -vulkan
11615 frames 48.907 seconds 237.49 fps ( 4.21 ms/f) 28.316 fps variability

As you can see, 64-bit Vulkan on Win 11 hits a higher framerate, but with only a bit more variability.

edit: Live long and prosper

[DukeyNukey]

the command is -vulkan. you're doing it wrong.

[ＪＯＫＥ☆T☆ＲＡＩＮ]

Originally posted by icemanwest:

Originally posted by ඞ amogus ඞ:

the command is -vulkan. you're doing it wrong.

Are you trolling, I don't understand?

I could ask you the same thing.

[imw]

Originally posted by ඞ amogus ඞ:

the command is -vulkan. you're doing it wrong.

Understood, I think it was just a typo in my post. I'll run it again to be extra sure.,

[imw]

32-bit, Windows 11, no launch options
11615 frames 54.157 seconds 214.47 fps ( 4.66 ms/f) 25.375 fps variability

64-bit, Windows 11, no launch options
11615 frames 49.350 seconds 235.36 fps ( 4.25 ms/f) 28.586 fps variability

64-bit, Windows 11, -vulkan
11615 frames 49.486 seconds 234.71 fps ( 4.26 ms/f) 24.983 fps variability

Never attribute to malice what one can blame on being a fan of Star Trek :)

[DukeyNukey]

Originally posted by ＪＯＫＥ☆T☆ＲＡＩＮ:

Originally posted by icemanwest:

Are you trolling, I don't understand?

I could ask you the same thing.

someone actually asked something that dumb? how do you even troll over a typo?

[imw]

Originally posted by ඞ amogus ඞ:

Originally posted by ＪＯＫＥ☆T☆ＲＡＩＮ:

I could ask you the same thing.

someone actually asked something that dumb? how do you even troll over a typo?

It's fine. Everybody has a different way of asking questions or pointing out mistakes. I don't take any offense since it was an honest typo on this post.

[DukeyNukey]

i didn't mean it in a mean way, a lot of people make that typo so it's quite common although i'm surprised it had little to no difference for you.

[imw]

Originally posted by ඞ amogus ඞ:

i didn't mean it in a mean way, a lot of people make that typo so it's quite common although i'm surprised it had little to no difference for you.

Yeah, and having that pointed out did make me think that the maybe I did use -vulcan and so on the second try -vulkan really didn't make any difference as you note.

Upshot: Vulkan is on par with DirectX???

It would be great to see Win10 results and more modern GPU's.