> Hello all, > > Since someone started with the MultiLang I'm > going to continue. There has been a thing > that has really bothered me in the MultiLang - > replication. After the DB conversion it's > virtually impossible to upgrade packages.
What do You mean with "upgrade packages" ? > (Note: I've been lazy and have not tested > David's Repligard patch...) > > Another thing that troubles me is the performance. > Do we have any statistical data on how regular > Midgard site fares against MultiLanged site? > (Even if the MultiLang is not really used.) > > We've had some serious performance issues on > one of our servers and have planned on downgrading > back to regular DB format. BTW: Is there any script > available that would do the DB conversion backwards? Nope. But I was wondering about create something to make new midgard-data package be usefull for nonML <-> ML. Whatever it will look like , it will be looong time running. > The plan is to run Siege on the site just to > see if the MultiLang is causing any slowness. > Since I believe it will take some time to > get a production server back-ported, I'd be > happy to see any statistics about regular vs. > MultiLang db even before we start the downgrading. First thing which comes to my mind is "collect" mysql queries either from mysql log file or midgard log file which may be created with new apache module, and compare queries' time. Or maybe something like 'time midgard-pageresolve -options'? BTW , I noticed slow performance with midgard 1.6 but compiled without Multilang , when one host uses another's one database. Both hosts are in the same network and use stunnel to secure connections. Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
