Microsoft Cognitive Toolkit 2.0 • Hacker News Board

Re: Microsoft Cognitive Toolkit 2.0

#51

Post by 75dvtwin » Sat, Jun 03, 2017, 7:43 PM UTC

75dvtwin wrote: post #33

ronjouch wrote: post #2

Also, "Reasons to Switch from TensorFlow to CNTK": https://docs.microsoft.com/en-us/cognitive-toolkit/reasons-t...

I did not know the below situation with tensor flow. MS contributions to OSS, at least in this instant, appear a lot more transparent and not-self-centered, compared to Google's "...It was made very clear from the first day of TensorFlow’s announcement, that Google created two TensorFlow versions: a public version and an internal version. As a TensorFlow user, one either must tolerate the slow speed of the public ver…

Thx for all the follow ups and clarifications. I am a user of neither toolkit yet, but following their progress. Perhaps submitting a bug to ask MS to change the above misinformation, is appropriate

Re: Microsoft Cognitive Toolkit 2.0

#52

Post by dgacmu » Sat, Jun 03, 2017, 9:51 PM UTC

moron4hire wrote: post #38

albertzeyer wrote: post #29

Earlier quoted context omitted.

This is because they use the CuDNN LSTM kernel in CNTK and in TensorFlow they chose to not use the CuDNN LSTM kernel which might be a bit unfair because they could have used it. The same for Torch. See here for more details: https://news.ycombinator.com/item?id=14473234

Why would that be "a bit unfair"? It sounds like the TensorFlow team just hasn't been able to make as many or as good of optimizations as the CNTK team. If they could have, but chose not to do the same things, what tradeoff is there to be able to say it's "a bit unfair"?

The binding of the word "they" is unclear in the comment you're replying to.

The "they" who chose not to use the cuDNN bindings were the authors of the benchmark. Some of the Torch folks filed a bug with the HKbench folks for the same error, but with respect to Torch: https://github.com/hclhkbu/dlbench/issues/14

Re: Microsoft Cognitive Toolkit 2.0

#53

Post by moron4hire » Sat, Jun 03, 2017, 10:33 PM UTC

dgacmu wrote: post #52

moron4hire wrote: post #38

Earlier quoted context omitted.

Why would that be "a bit unfair"? It sounds like the TensorFlow team just hasn't been able to make as many or as good of optimizations as the CNTK team. If they could have, but chose not to do the same things, what tradeoff is there to be able to say it's "a bit unfair"?

The binding of the word "they" is unclear in the comment you're replying to. The "they" who chose not to use the cuDNN bindings were the authors of the benchmark. Some of the Torch folks filed a bug with the HKbench folks for the same error, but with respect to Torch: https://github.com/hclhkbu/dlbench/issues/14

thanks, that makes more sense