Chris Mulligan wrote: > I agree with Noah. What's the problem this is really solving in the > real world? Why did you ever need a separate read database?
Not related to this general principle but i recently had to scale up a project I was running (totally unrelated to Trac) and if it had been coded with a separate read database it would have made my life a lot easier.... Using MySQL slaves for read operations and only hitting the master for writes would have made scaling up a lot easier. So this patch does definitely solve a real life problem with regards to load. Sure, most trac project wont get that busy (and with trac the bottleneck is usually at the python end rather than the SQL end), but the principle is not a bad one. Just a small €0.01 (I'll save the other €0.01 in the bank for later). Col. /me is happy he has finally gotten round to setting up his Google Groups account with the same address he uses on Gmane.... it just works(tm) yay!! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
