On Mar 23, 2009, at 9:05 AM, Ethan Mallove wrote:
-------------------+---------------------+----------
Resource | Unit | Unit cost
-------------------+---------------------+----------
Outgoing Bandwidth | gigabytes | $0.12
Incoming Bandwidth | gigabytes | $0.10
CPU Time | CPU hours | $0.10
Stored Data | gigabytes per month | $0.15
Recipients Emailed | recipients | $0.0001
-------------------+---------------------+----------
Would we itemize the MTT bill on a per user basis? E.g., orgs that
use MTT more, would have to pay more?
Let's assume stored data == incoming bandwidth, because we never throw
anything away. And let's go with the SWAG of 100GB. We may or may
not be able to gzip the data uploading to the server. So if anything,
we *might* be able to decrease the incoming data and have higher level
of stored data.
I anticipate our outgoing data to be significantly less, particularly
if we can gzip the outgoing data (which I think we can). You're
right, CPU time is a mystery -- we won't know what it will be until we
start running some queries to see what happens.
100GB * $0.10 = $10
100GB * $0.15 = $15
total = $25 for the first month
So let's SWAG at $25/mo for a year = $300. This number will be wrong
for several reasons, but it at least gives us a ballpark. For $300/
year, I think we (the OMPI project) can find a way to pay for this
fairly easily.
--
Jeff Squyres
Cisco Systems
