Skip to content
Discussion options

You must be logged in to vote

It's because the JIT is compiling your update() code, so it may not be easy to make it faster unless there's some low hanging fruit you can use the lax loop primitives with. Incidentally you may see a speedup if you move the optimizer.update call inside the JIT-ed region of code as well. It might also (not really sure) reduce peak memory usage since the non-JITTed update call will need to have the pre and post update versions of your parameters in your accelerator memory but the JIT should figure out that the update can be done in place.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by pvasired
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants