| 2 | | See [[https://ps1wiki.ifa.hawaii.edu/trac/wiki/PSPSClusterHardwareEstimate2015 | PSPS Hardware Plan C] Over the course of the ingest and merge, the only thing that will significantly vary as we ingest across the sky is |
| 3 | | the cumulative size of the merged database. Each subsequent addition prior to merge, will be about the same size, and will be handled by a similar machine. Our greatest uncertainty at this stage is the scaling with the total size, not the scaling per chunk. This page describes a "datastore tessellation". |
| | 4 | See [https://ps1wiki.ifa.hawaii.edu/trac/wiki/PSPSClusterHardwareEstimate2015 | PSPS Hardware Plan C] Over the course of the ingest and merge, the only thing that will significantly vary as we ingest across the sky is the cumulative size of the merged database. Each subsequent addition prior to merge, will be about the same size, and will be handled by a similar machine. Our greatest uncertainty at this stage is the scaling with the total size, not the scaling per chunk. This page describes a "datastore tessellation". |