4 ms·

> Are you saying the cost of encryption is affordable for everybody because it is for Google? On top of that, it assumes everybody has the latest processors. I

by amyjess 12y ago

> Are you saying the cost of encryption is affordable for everybody because it is for Google? On top of that, it assumes everybody has the latest processors. In reality, people don't upgrade their computers every year. Worse, it's people with older computers who need to eke out every bit of performance their processors offer. Like, sure, I can afford to burn CPU cycles because I have a Haswell i7, but someone with an old Core 2 can't, and they're the ones who will have to burn CPU on encryption, and I don't need to because my powerful CPU has AES-NI.

thomashabets2 12y ago
If you don't have AES-NI, then you don't have much traffic. Otherwise you would have bought newer servers. And you therefore don't have a problem either way.
- untitaker_ 12y ago
  I don't use encryption for media streaming on my Raspberry Pi because the lack of hardware support for crypto means the download rates drop from 70 to 7 Mbit/s. I won't spend money on the new model because people on the internet tell me streaming cartoon series is sensitive traffic. There you go, a counterexample for your blatant overgeneralization.
  - thomashabets2 12y ago
    :-) I seem to remember getting 50-70Mbps with SSL on my Raspberry Pi (not RPi2). I had to tweak my cipherlist, but not to anything unreasonable insecure. The limiting factor there though was by far the USB hard drive attached. Banana Pi has SATA onboard, and not a NIC that's attached over the USB bus, so I'd recommend that in most cases.
    - untitaker_ 12y ago
      I wondered if I did anything wrong with the setup, so I'd be really interested in your cipher list. I did read some benchmarks on the internet though.
      - thomashabets2 12y ago
        It was most likely upping the prio of RC4, to select that. It's been a while though.
  - amyjess 12y ago
    On top of that, encryption adds client-side overhead as well.
    - untitaker_ 12y ago
      Oh, I wouldn't really care about client-side overhead -- that one scales itself, and in my particular example the machines I use are powerful enough.

by amyjess 12y ago

thomashabets2 12y ago

If you don't have AES-NI, then you don't have much traffic. Otherwise you would have bought newer servers. And you therefore don't have a problem either way.

untitaker_ 12y ago
I don't use encryption for media streaming on my Raspberry Pi because the lack of hardware support for crypto means the download rates drop from 70 to 7 Mbit/s. I won't spend money on the new model because people on the internet tell me streaming cartoon series is sensitive traffic. There you go, a counterexample for your blatant overgeneralization.
- thomashabets2 12y ago
  :-) I seem to remember getting 50-70Mbps with SSL on my Raspberry Pi (not RPi2). I had to tweak my cipherlist, but not to anything unreasonable insecure. The limiting factor there though was by far the USB hard drive attached. Banana Pi has SATA onboard, and not a NIC that's attached over the USB bus, so I'd recommend that in most cases.
  - untitaker_ 12y ago
    I wondered if I did anything wrong with the setup, so I'd be really interested in your cipher list. I did read some benchmarks on the internet though.
    - thomashabets2 12y ago
      It was most likely upping the prio of RC4, to select that. It's been a while though.
- amyjess 12y ago
  On top of that, encryption adds client-side overhead as well.
  - untitaker_ 12y ago
    Oh, I wouldn't really care about client-side overhead -- that one scales itself, and in my particular example the machines I use are powerful enough.