GPU Benchmark #71
Replies: 2 comments
-
|
Just a note that in practice we typically need to use annual rates (in my company) as underwriting loadings are supplied as factors on the annual rates. You might find performance improves by using log and exp instead of power as they are optimised, i.e. and for 1-a There is a numpy/julia function I tried out this on my numpy vectorised model and got a noticable boost. I'm currently writing a version of the model in mojo and will see how they make a difference there. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry I somehow didn't see this post, I saw the branch a while ago but saw it wasn't ready and was going to wait for it to be ready. I did not intend to leave this unanswered for 2 months. Caching the exponentiated rates is a very nice idea. Y'all (@alecloudenback, @lewisfogden) are now admins. If you feel modifications should be made to the GPU benchmarks feel free to. I really shouldn't have been so slow to reply, if any PRs are made I'll be available for review. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@MatthewCaseres some misc observations:
^). Precomputing the rates to be monthly (see the_mthversion in WIP: Julia Basic_Term_ME #70) cuts 10million policies down to about 16 seconds.At some point I'll create a GPU version to compare but I am not super focused on this right now, but thought you would be interested in some of the above observations.
Beta Was this translation helpful? Give feedback.
All reactions