4 ms·
Who is "we"? I might be another customer :) I meant rsh, not ssh, wasn't trying to stick extra processing in there. Debian, bless 'em, still support rsh, I th
by luckydude 16y ago
Who is "we"? I might be another customer :)
I meant rsh, not ssh, wasn't trying to stick extra processing in there.
Debian, bless 'em, still support rsh, I think it's rsh-clients and rsh-server.
For your 300Mbytes/sec, what's the network? And is the data in memory or on disk? If on disk, what sort of drives and what size files?
Thanks!
- fragmede 16y agoIt's a product for a niche B2B market, but if you're buying, email's in my profile ;) The network is 10-Gigabit ethernet, from server to a switch, then switch to client, all via CX-4 or SFP+. The data is actually coming off disk at that rate (in ram would be cheating :p ). It's backed by a 16-drive hardware raid using 2TB spinning disks (SATA) in a raid5. The performance we sell is actually 2 streams of read while simultaneously writing a stream to disk, so 600 out, 300 in. The files are actually the hard part. This supports the dpx 'video' format. The format originated from film scanners, and so each frame is (basically) a 12.5 MByte jpeg. Multiply that by 24-30 fps, add in overhead for reading that many files/sec, and you get 300+ MBytes/sec. (This is also why I'm so sure there's more performance to be had if you don't have the same overhead.)