-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Track benchmarking #16
Comments
Rebuilt (versions as described above) and submitted as a job to a Cascade Lake node, using my update_resnet_example branch: For the single image given to ResNet, FTorch seems comparable, perhaps slightly faster:
For large stride, FTorch seems significantly faster:
For cgdrag, FTorch is seems worse, although less so than seemed to be the case in #11 (<10%).
|
Same binaries, but on an Icelake node: ResNet - very similar, with FTorch very slightly faster with more threads:
Large stride - FTorch significantly faster:
cgdrag -smaller (<5%) differences, mostly with FTorch slower, although FTorch fractionally faster with OMP_NUM_THREADS=8:
I'll try rebuilding with Intel compilers next? |
Swapping out the Fortran compiler seems to give a similar picture, although they generally seem to be slower:
ResNet:
Large Stride:
cgdrag:
|
Thanks @ElliottKasoar this looks great. Can we expand the timing functionality to time:
For now, we can focus on cgdrag and resnet tests only. |
We also need to remember, once we have added better timing, we need to compare forpy running with TorchScript compiled model and calling python environment. This is enabled/disabled using CMake flag |
To close this issue we can produce a notebook with some test results for ResNet and cgdrag models, once we have increased the significant figures of timings |
Since #11 will hopefully be merged relatively soon, we can keep track of new benchmarks here.
I intend to rebuild to double check versions for everything, but my first set of results on CSD3, run interactively on a single Cascade Lake node (
sintr -p cclake -N1 -n8 -t 1:0:0 --qos=INTR
), with:module load gcc/9
(9.3.0)module load python/3.8
(3.8.2)are not particularly conclusive:
The text was updated successfully, but these errors were encountered: