• 8 Votes
    2 Posts
    2k Views
    scaleS

    We are very happy to see these. Nearly 11K Read IOPS, that's awesome.

  • 4 Votes
    48 Posts
    10k Views
    scottalanmillerS

    @Dashrender said:

    @scottalanmiller said:

    @Dashrender said:

    @scottalanmiller said:

    @Dashrender said:

    Scott, you mentioned that this is all at the kernel level - could you roll your own version of this?

    Sure, you'd have to write your own storage layer, though. So it's not trivial in any way.

    OH.. that's where I was confused I guess... I thought the storage layer was part of KVM (that's the hypervisor they use, right?)

    Not part of KVM itself. The Scale HC3 is unique, there is no software version available on the market.

    So they wrote the storage layer? Cool - good to know/understand that.

    Yes, Scale is primarily a storage vendor. Before they made their Hyperconverged product, they made scale out storage only. That was before KVM was mature enough to make the HC3 product. They no longer sell the storage layer, it is now developed purely and designed solely around the needs of the HC3 product so is completely unique to that. It's the storage layer and the storage integration (and support) that are their selling points. That's what makes them special and unique. KVM and the hardware on its own you could do yourself and you could easily make due with a different interface.

  • 0 Votes
    56 Posts
    18k Views
    larsen161L

    @scottalanmiller

    @scottalanmiller said:

    We need some latency numbers from around the world. Anyone want to collect some for us?

    Here is the first IP address. A long running ping (hundreds or thousands of pings) would be good, we need the final stats from that:

    104.236.119.59 108.61.151.173 172.99.75.133

    We have a good idea on bandwidth, IO, CPU and memory. Network latency is pretty huge.

    1,200,000 packets later...
    via rackspace 8 GB General Purpose v1 based in london

    --- 162.242.243.171 ping statistics --- 400510 packets transmitted, 400499 received, 0% packet loss, time 400849652ms rtt min/avg/max/mdev = 79.018/79.634/184.775/2.778 ms --- 104.236.119.59 ping statistics --- 400759 packets transmitted, 400732 received, 0% packet loss, time 401132556ms rtt min/avg/max/mdev = 73.663/74.533/191.571/2.203 ms --- 108.61.151.173 ping statistics --- 400765 packets transmitted, 400749 received, 0% packet loss, time 401117767ms rtt min/avg/max/mdev = 69.861/75.792/205.164/3.167 ms