85 karma · joined March 24, 2014
Totally agree about ONNX, without it I wouldn't probably even started making this library. However, something I want to try is to code the network with Nx/Axon, without using onnx. The main advantage I see moving from onnx to Axon is to take advantage of all the new cool stuff like Nx sharding: https://dockyard.com/blog/2024/11/06/2024/nx-sharding-update...
This time we are going to process on the fly a 30 million lines remote file, summing the numbers of each line. We will see how to implement the functions we need to convert a stream of chunks (the one built in the part 1) to a stream of lines. We'll then run a benchmark of two different implementations.
We will then see how easy and quick is to process just the first 30 lines of the same 125mb remote file.
The most passionate will find a small challenge at the end.
In this video we see pattern matching with tuples, lists and maps, a bit of control flow and recursion.
So, the "sublicense this right to third parties" I think is because we are storing the files on S3. I see, this phrase doesn't look good .. do you think it would be better to explain sublicense to amazon for the storage, or even better get rid of this ?
About the "perpetual", if would be "10 days" , which is the expiration time for every transfer, would it better?
Cheers