@ynot it’s kind of hard to tell what you’re doing. If I can’t run it I can’t help you. I can’t reverse engineer your whole context just from a process screenshot. I can only guess which means my answer will probably be wrong due to missing details and I can’t read minds. (eg: I can’t see your code)
Code without configuration and context doesn’t really help anyone help you.
With that in mind, please follow up with more details.
Start with describing everything about what you are running. That includes the web framework you’re using, how you are running the rest api
Give more details about what you think fast should be. What are we talking here? Throughput? Records per second? Let’s establish a metric to to measure so we can clearly say yes or no if the support here clearly made your model faster after a bit of discussion.
Let me suggest a few things:
Tell me what you think fast should be. Where does it start? What does it slow down to? If you don’t know how to measure performance please use the performance listener.
How are you running a benchmark? Are you just letting some training code run? I would advise giving me a clear way to reproduce your benchmark. Usually that will come down to seeing all of your code including your data pre processing.
In order to make sure you’re using the latest dl4j please include an mvn dependency:tree dump of all your dependencies as a github gist so we can make sure it’s using the latest.
Since I have another question and this does not fit to the topic, I will have to open a new one and would like to explain more details about my approach