tag:blogger.com,1999:blog-16959946.post826867274017850650..comments2023-12-09T16:44:47.897+01:00Comments on The Data Charmer: How fast is parallel replication? See it live todayGiuseppe Maxiahttp://www.blogger.com/profile/15801583338057324813noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-16959946.post-16938122687273206712011-03-17T16:25:40.111+01:002011-03-17T16:25:40.111+01:00p.s., I would be very interested in talking more d...p.s., I would be very interested in talking more deeply with your team about parallel and multi-master replication features. With some small feature additions I believe drizzle could be very good at these problems.Robert Hodgeshttps://www.blogger.com/profile/05379726998057344092noreply@blogger.comtag:blogger.com,1999:blog-16959946.post-54335695165111579782011-03-17T16:23:34.461+01:002011-03-17T16:23:34.461+01:00Hi Stewart,
First of all congrats on the new rel...Hi Stewart, <br /><br />First of all congrats on the new release. <br /><br />Are per-catalog logs necessarily separate files? If so, then having a lot of them would make logging very slow unless you are on a device that works well with random I/O. You have the same issue when reading from them. <br /><br />Also, parallel apply has a number of non-trivial problems around recovery, serialization of updates between dependent databases (common in multi-tenant apps) and avoiding serialization points on I/O etc.Robert Hodgeshttps://www.blogger.com/profile/05379726998057344092noreply@blogger.comtag:blogger.com,1999:blog-16959946.post-53905667232372177682011-03-17T14:43:40.221+01:002011-03-17T14:43:40.221+01:00for drizzle, if we enable per-catalog replication ...for drizzle, if we enable per-catalog replication logs, doing parallel apply should be trivial. This solves the multi-tenancy problem of having other users introduce latency in replication. It doesn't (of course) solve the single db/table high workload problem though (much trickier).Stewart Smithhttps://www.blogger.com/profile/00989044306462002000noreply@blogger.com