Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CDC File Transfer

github.com

Post reply on HN
Print view View original

151–160 of 229 posts

Re: CDC File Transfer

#151

Post by ljusten »

verdverm wrote: post #114
disqard wrote: post #109

Earlier quoted context omitted.

Yes, this was a core architectural requirement of Stadia (running the games on Linux), as opposed to hosting virtualized Windows machines (which would've allowed serving up Windows-based games). Whether this specific design choice alone killed Stadia, no one can say -- but it was probably one of the most important factors in its demise.

Input lag and pixelated graphics is why I quit, I had gigabit fiber at the time

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.

Re: CDC File Transfer

#152

Post by ljusten »

c7b wrote: post #150
ljusten wrote: post #138

Earlier quoted context omitted.

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 haven't tried those). We then used https://ezgif.com/optimize to remove dupe/unwanted frames, tweak timings and compress the gif. The actual content was done in Google Slides.

Awesome, thanks for replying here! If I may be greedy: I suppose you used something else for capturing the command prompt gif?

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 had been in the office that day.

Re: CDC File Transfer

#153

Post by ljusten »

worldsavior wrote: post #144

Why is it only from windows to Linux?

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.

Re: CDC File Transfer

#155

Post by piceas »

ddalex wrote: post #140
cwaffles wrote: post #99

CDC slides explaining the algorithm: https://www.usenix.org/sites/default/files/conference/protec...

What I don't get is how are the Gear CDC constants (the lookup table for gears) generated. Any insight ?

The fastCDC paper says they used random values.

"It employs an array of 256 random 64-bit integers to map the values of the byte contents in the sliding window"

I presume using something else would skew the distribution of selected chunks. I don't know if that would help or hinder.

In my very limited experience, a picture of Rick Astley as the constants gave a similar distribution™ of chunks over a mixture of documentation files and Linux ISOs.

Re: CDC File Transfer

#156

Post by jamespo »

ljusten wrote: post #153
worldsavior wrote: post #144

Why is it only from windows to Linux?

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.

And linux to linux?

Re: CDC File Transfer

#157

Post by worldsavior »

ljusten wrote: post #153
worldsavior wrote: post #144

Why is it only from windows to Linux?

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.

But why not make cross platform? If already creating a file transfer program, make it cross platform. What're the complications?

Re: CDC File Transfer

#158

Post by skies457 »

c7b wrote: post #130

Slightly OT, but I like the schematic gifs used in the Readme.md (pretty amazing doc overall!) like this one [0]. Does anyone have suggestions what tools they might have used (or might be used in general) to create those? [0] https://github.com/google/cdc-file-transfer/blob/main/docs/l...

D2 (https://d2lang.com/tour/intro/) might be the tool you are looking for, but it doesn't handle animation as far as I know

Re: CDC File Transfer

#159

Post by aembleton »

hot_gril wrote: post #69
josephg wrote: post #57

I'm really impressed with the readme file in this repository. Its a master class in effective documentation. Just look at the structure: - 1-2 sentence summary of the project - History (why we built this and didn't just use existing tools) - What we've built, including what it does and how it compares to other tools (rsync in this case). - How to install and use it And the whole thing is full of images and animations…

This is how I strive to document things. Focus primarily on what the tool is used for and why, not trying to define what it is.

Also for commit messages - why the change is made, not what it is.

Re: CDC File Transfer

#160

Post by mattlondon »

disqard wrote: post #109
winrid wrote: post #106

So game devs had to port their games to Linux to run on Stadia servers? That seems like a huge bottleneck...

Yes, this was a core architectural requirement of Stadia (running the games on Linux), as opposed to hosting virtualized Windows machines (which would've allowed serving up Windows-based games). Whether this specific design choice alone killed Stadia, no one can say -- but it was probably one of the most important factors in its demise.

What killed stadia (IMO) was that you could not access your existing steam library.

Nvidia allow this (kinda - some publishers do not allow their games to be played which is annoying), and I happily pay for it.

Post reply on HN