couchdb - Can a database be considered idle even when continuously replicating? -
i'm considering couchdb project (still in research phase). want many users, each own database (for authentication purposes), 1 big read-only database they're replicated, can generate reports , make dashboard. let's assume databases running on same machine , in same process.
normally, small fraction of human users online , doing things, should able keep max_dbs_open setting lot lower total number of users. couchdb should have no problem determining ones idle.
however, i'm worried database throw wrench this. having continuous replication user databases 1 big database keep them awake time? (and if so, bad? logged-in users lose priority advantage , thrashed @ bad times?)
or couchdb smart enough consider database idle long it's not being queried or written to, if there's ongoing continuous replication session? note replication in 1 direction: big database watches changes user databases.
suggestions other ways approach problem welcome. i'm vaguely aware if i'm going have enough users problem, 1 database going unwieldy beast.
thanks!
Comments
Post a Comment