It's budget bidding time and we need to bid for some money to move this pilot project into a production service. So as we're piloting a repository we need a system capable of delivering the content to the students. The problem is that we're running a pilot so we've got early adopters using the system who are keen and have lots of data. So we don't really know how that will scale to a general purpose system. We also won't have the production release of the software until February so we don't know what kind of load it will put on the server. Obviously by the end of the project we will have a much better idea of what we need to run the production system but we need to bid for the budget now.
We summarised our current knowledge as:
Size of database: Big
Network bandwidth required: Lots
CPU throughput: Fast
Disk throughput: Big, Fast and lots of flashing lights
and of course we need two of them to give us high availability in the face of a hardware or software failure.
We stuck our finger in the air and hung some seaweed out the window and came up with a number that covers as many contingencies as possible without it looking like we trying to buy a small island in the Caribbean.
Keywords: budget disks network
No comments:
Post a Comment