I'm interested in understanding how Laconica scales. From what I can
tell, the main idea is that Laconica scales by allowing lots of
different sites work together in a federated way. This means that
anyone can setup their own instance of laconica. That instance of
laconica can connect to other instances of laconica by forwarding
updates.
This means that a user of a particular instance of laconica, say
identica, can get updates from someone using a different instance of
laconica, say decafbad.
Are there any existing examples of federated copies of laconica
running? Is the subscription sitewide or on a user by user basis.
For example, would the public timeline of one site be replicated to
the subscribing site?
How does one user subscribe to a user on another instance of laconica?
I'm also curious how a single instance of Laconica would scale. Say
identica became very popular and was getting overloaded, how would one
scale that particular instance of laconica? My guess is that the
bottleneck would be the database access and that going some master/
slave architecture would be a first step. Is the underlying code
written to support this kind of scaling? Is anyone running an
instance of laconica with more than an single database server?
I notice that the table types are MyISAM. This is probably so MySQL
full text search can be used. Of course this won't work very well
once the notice table gets large (millions) and/or the update rate
increases. MyISAM uses full table locks. This means that the entire
table is locked when an update is added to the notify table. Lots of
full table locking means things will get slow when you have lots of
updates, especially on a large table.
Sorry to ask so many questions!
Regards,
Adam
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
