Labs/Weave/Service/Scaling/Projects/Aragog: Difference between revisions

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.
# 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.
# 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.
canmove, Confirmed users
1,173

edits