3 ms·

JS is mostly 'unsuitable' because of the lack of integration into GPGPU. This is one of the reasons I was hoping WebCL[1] (now dead[2]) would take off. It wou

JS is mostly 'unsuitable' because of the lack of integration into GPGPU. This is one of the reasons I was hoping WebCL[1] (now dead[2]) would take off. It would have enabled GPGPU work that is pretty much a prerequisite for anything that would be taken seriously by the community. There was talk of ARB_compute_shader support as mentioned in the second ref link, but I haven't seen anything else in that area. [1] https://www.khronos.org/webcl/ https://www.khronos.org/webcl/ [2]https://bugzilla.mozilla.org/show_bug.cgi?id=664147#c30 https://bugzilla.mozilla.org/show_bug.cgi?id=664147#c30

onion2k 10y ago
JS is mostly 'unsuitable' because of the lack of integration into GPGPU. Does that mean that using an already trained model would be slow? If I wrote something to train a model on a GPU, could I then export the data to use with JS in a browser?
- steplee 10y ago
  Training is essentially running the net forward then backward on many training examples. Using the model is running it forward on one input, so it would be much faster depending on your specific model and use cases