ljusten

4 ms·

1.
by ljusten 4y ago
The same question was asked here: https://github.com/google/cdc-file-transfer/issues/56
2.
by ljusten 4y ago
Short answer, we didn't need it. While the code is largely cross-platform, there is some work involved when it gets down to the details. We are currently working on supporting Windows to Windows. Linux to Linux has lower priority as rs
3.
by ljusten 4y ago
Note that cdc_rsync runs on Windows and syncs to Linux. rsync is a Linux-only tool where you'd have to jump through some hoops to make it work on Windows.
4.
by ljusten 4y ago
Just the compiled and baked game, not your sources. You still developed on Windows or wherever, the cloud instance was just used for running the game.
5.
by ljusten 4y ago
Windows to Windows is being worked on, see https://github.com/google/cdc-file-transfer/compare/main...s... . Linux to Linux is also an option if there is demand, but currently it's Windows to Linux only.
6.
by ljusten 4y ago
We're currently adding support for Windows to Windows to cdc_rsync. If there is demand, Linux to Linux would also be possible.
7.
by ljusten 4y ago
Just uncompress the binaries on the Windows machine and run cdc_rsync. The Linux component, cdc_rsync_server, is deployed automatically on first run. It is scp'ed to ~/.cache/cdc-file-transfer/bin. So nothing has to be i
8.
by ljusten 4y ago
I should also note that we used a fairly fast 100 MB/sec connection to upload the data, so the rsync diffing algorithm running at 50 MB/sec is actually a bottleneck. The difference would be smaller on a slower connection, where th
9.
by ljusten 4y ago
IIUC, rsync computes a relatively expensive Rabin-Karp rolling hash ( https://librsync.github.io/rabinkarp_8c_source.html ) and performs a hash map lookup for every byte. Hash map lookups might not be very cache friendly for
10.
by ljusten 4y ago
For reference, here's the paper that describes the in-place update algo in rsync: https://www.usenix.org/legacy/events/usenix03/tech/freenix03... . I haven't looked into it more deeply, but I th
11.
by ljusten 4y ago
This is currently being worked on, see https://github.com/google/cdc-file-transfer/compare/main...s...
12.
by ljusten 4y ago
That's because most Stadia devs used Windows, but the cloud instances ran on Linux, so devs had to copy their games from Windows to Linux. We're currently adding support for Windows to Windows as well.
13.
by ljusten 4y ago
Nope, luckily we still partially work from home and use Chrome Remote Desktop. The command prompt was running on my Windows machine, which I accessed remotely, so I could capture it with the extension. That wouldn't have worked if I ha
14.
by ljusten 4y ago
I got the same when I was running Stadia on a 2.4 GHz wifi network. Once I switched to a wired connection, it worked like a charm. 5 GHz supposedly works as well, but my robot vacuum cleaner needs a 2.4 GHz network facepalm .
15.
by ljusten 4y ago
In a nutshell, the algorithm computes uint64_t hash = 0; uint64_t magic_pattern = 0b001000010000100001000...; for (size_t n = 0; n < data.size(); ++n) { hash = (hash << 1) + random_table[data[n]]; if ((hash & ma
16.
by ljusten 4y ago
>> Or, how is it that the local manages to be clairvoyant enough to choose the same windows? Yes! In content defined chunking, the chunk boundaries depend on the content, in our case a 64 byte window. If the local and the remote files
17.
by ljusten 4y ago
We used an internal Chrome extension to capture the gifs. There also seem to be some externally available GIF capturing tools, like https://chrome.google.com/webstore/detail/chrome-capture-scr... (disclaimer: I ha