(Illustration by Gaich Muramatsu)
On Wed, Jul 03, 2002 at 09:51:34AM -0600, Matthew Excell wrote: > One of those 7 clients puts a small PostgreSQL database in the coda tree > - Only one client will ever access it at a time, but it needs to be in > coda since the machine that accesses it may change. Creating a database > - something that takes on the order of 500ms without coda - takes 2-3 > minutes. Creating a table takes the same kind of time. > > Question: will write-disconnected operation help? Is it safe? What else > can I tweak to fix this? The setup is just an out-of-the-box install . If you run 'codacon' you should see a it of what the Coda client is trying to do. If there are a lot of 'Store' operations while the database is created, especially when these are all for the same (set of) files, write-disconnected operation will help a lot, because the unnecessary intermediate stores are optimized away. It is about as safe as what you are doing now. As soon as another machine is accessing the database read/write you are going to get conflicts either way. JanReceived on 2002-07-03 12:23:21