Once a pad gets past about 10k changesets a noticable lag starts creeping into a pad if you are on a fast network.
Once a pad gets past about 25k changesets this gets nearly unusable from a UX perspective.
Using etherpads for daily scrums for a 12 person team means we have to rotate pads about every 2 weeks otherwise the pads aren't usable. It would be nice if this didn't degrade so badly over time.
Perhaps changesets could be stored more in a RevLog like format which would give more constant time in moving through and accumulating history - http://mercurial.selenic.com/wiki/Revlog
Using latest etherpad (1.2.4) and nodejs 0.8.
Once a pad gets past about 10k changesets a noticable lag starts creeping into a pad if you are on a fast network.
Once a pad gets past about 25k changesets this gets nearly unusable from a UX perspective.
Using etherpads for daily scrums for a 12 person team means we have to rotate pads about every 2 weeks otherwise the pads aren't usable. It would be nice if this didn't degrade so badly over time.
Perhaps changesets could be stored more in a RevLog like format which would give more constant time in moving through and accumulating history - http://mercurial.selenic.com/wiki/Revlog