Hello,
I have a question about how to read theano profiling results. I am running
a RNN model, where the gradient is calculated via theano.scan. When I
profile the code, I can see that the bulk of time is spent on theano.scan.
Moreover I notice that the type of call is Py rather than C.
My qu
Thank you for the response. It helps a lot.
--
---
You received this message because you are subscribed to the Google Groups
"theano-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to theano-users+unsubscr...@googlegroups.com.
For more options, vi
Hi,
I am running a RNN/GRU model for a fairly large dataset with the goal of
sequence prediction. When I profile my code, I found one GpuFromHost takes
~30% of computation time. See part of profiling results below:
<% time><#call>
30.2%73.0% 462.776s 3.71e-01s 1248
:
x = T.ivector()
z = T.cast(y, dtype='int32')
Do you think these things cause the problem?
Thank you,
Haining
Haining Yu on Gmail
On Wed, Aug 9, 2017 at 2:36 PM, Frédéric Bastien wrote:
> My guess is that you use the old GPU backend. Can you confirm you use the
> Theano flag
you end up with float64, it is frequently that case.
> Fred
>
> On Wed, Aug 9, 2017 at 2:48 PM Haining Yu >
> wrote:
>
>> Thank you Fred.
>>
>> Yes I am using device=gpu0. I will switch to the new backend and test
>> again.
>>
>> On float64, do
