505
edits
Labs/Weave/Service/Scaling/Projects/Aragog: Difference between revisions
Labs/Weave/Service/Scaling/Projects/Aragog (view source)
Revision as of 20:27, 14 September 2009
, 14 September 2009no edit summary
(Created page with 'This project is first in a series that are aimed at scaling services. The scope of this project is to get a production quality Sync 1.0 service capable of handling at least 1 mi…') |
No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 31: | Line 31: | ||
=== Server === | === Server === | ||
# | # The biggest challenge is that the process appears to be binary right now - the system is fine, or it's melting down, and there's no gradual increase that would indicate there's a problem that needs attention soon. We can try to figure out where that tipping point is, but also need to explore why the problem is so binary. | ||
# Greater use of memcache on frequent small calls (notably /info/collections. We might also build it into /node/weave on the user side. | |||
# Flatter DB structure, recognizing that this is currently a write-heavy system. Once it matches a more read-heavy system, we can extend the slave configuration to add reads. | |||
== Infrastructure changes == | == Infrastructure changes == | ||
| Line 45: | Line 46: | ||
# Create operations runbook. | # Create operations runbook. | ||
# Committed owners/backups for key pieces of infrastructure. | # Committed owners/backups for key pieces of infrastructure. | ||
== Other == | |||
# Get staging environment set up and ready to go. | |||
# Get extra capacity for 1.0 Beta and beyond based on #1 above. | |||
# Train rest of IT during IT onsite (Oct?) | |||
# Plan out h/w requirements through 1H10. | |||
# Set up Cassandra to get next gen DB investigations going. | |||