Confirmed users
381
edits
Telemetry/Reboot: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* Ability to process 10x incoming packet rates of metrics telemetry infrastructure on a single AWS instance: 2400req/s with 30K HTTP POST packets. Fall | * Ability to process 10x incoming packet rates of metrics telemetry infrastructure on a single AWS instance: 2400req/s with 30K HTTP POST packets. Fall | ||
* Server should be bandwidth-limited, not CPU. | * Server should be bandwidth-limited, not CPU. | ||
* Server should make data available for map/reduce immediately. Fallback goal: 5min latency | * Server should make data available for map/reduce immediately. Fallback goal: 5min latency. In Q4 we'd like to use something like heka to make dashboards use live data(0min lag). | ||
Server Milestones: | Server Milestones: | ||