sionnaRT: slow GPU computation times about sionna

[SebastianCa]

Hi @bchateli,
I have tried to reproduce the observed behavior using Sionna version 0.16.2 on my machine, but I wasn't able to see the same results.
Have you tried to run the code snippet in GoogleColab? Can you please tell us about your setup?

[bchateli]

Hi @SebastianCa,

I just tried the snippet in GoogleColab and, like you, I am not able to reproduce the behaviour.

It must be related to my setup. I am running Sionna 0.16.1/2 on Windows 10, with Python 3.9.16 and Tensorflow 2.10.1. I tried more recent TF versions but I haven't been able to make it work on GPU.

[merlinND]

Hello @bchateli,

One idea to identify the source of the slowdown: if you fix all of the inputs (e.g. by fully controlling the randomness, or by setting some hardcoded values) and run the simulation multiple times, do the subsequent runs get faster?
We expect the very first run to be slower because there is a just-in-time compilation step, but after that the compiled kernel should be reused.

[bchateli]

Hi @merlinND,

Thank for the idea, I will try and get back to you.

I compared my setup with the one in Collab and suspect it might related to the old TF version I am using (2.10.1 vs 2.15.0 for Collab). However, TF does not maintain GPU support on native Windows past 2.10 versions, so I'd have to test on WSL.

[bchateli]

To get back to your suggestion @merlinND, I ran the simulation (on GPU) 3 times on the same console, and I got almost the same time for each run (plus/minus 1s)

[merlinND]

Hello @bchateli,

I am unable to reproduce on my machine as well. The GPU runtime is roughly 0.3-0.5 s on my machine, and CPU was ~0.5 s.

[bchateli]

Hello @merlinND,

Thanks for the return. Did you run it on Linux or Windows ?

My hypothesis is that it is related to the old GPU-compatible TF version that I use on Windows. I tried to reproduce it on WSL, but so far, I haven't been able to make the GPU work with TF in WSL.

[merlinND]

Hello @bchateli,

I ran my test on Linux (Ubuntu 22.04).

[SebastianCa]

Closing this issue as it appears to be related to using an outdated version of TensorFlow.