I only became interested in this because of the discussion in another thread, “How to attract more customers”, where this was posted:
One SNO I talked with said they are getting hundreds of thousands of requests every day for 256 bytes, sometimes 512 bytes (about 10-20%), with an offset into a piece. For that to happen, a customer must be doing very small ranged gets. As a customer, I would expect that if I read 10 bytes, I get billed for 10 bytes; not 9K. My actual concern was that the customer was getting billed only for the bytes he read, but Storj was paying for all the overhead, so Storj was paying 900x more to SNOs than it was receiving for this download.
Sure, it doesn’t matter if I do 1000 of these in a test. But when there are millions of downloads like this every day, it matters.
I’m glad Storj is not paying out more than it is receiving from the customer, and will admit this is a crazy use of Storj. On the flip side, this customer is paying Storj WAY more than he would on other services that only charge for the bytes actually received. If he’s reading 90 bytes per request for example, he is paying Storj about 100x what he would pay on competing services.
Not when there are millions of requests per day
I agree, it makes more sense for Storj, but it doesn’t make sense at all for the client. The client is paying for Storj’s backend overhead.
I’m done beating this horse, and glad your customer with millions of small downloads isn’t causing Storj a financial hardship.