On Sun, 2009-05-10 at 23:45 +0800, Timothy Lee wrote: > JohnS wrote: > > On Fri, 2009-05-08 at 15:33 +0100, Karanbir Singh wrote: > > > >> Timothy Lee wrote: > >> > >>>> What about it ? Does it address the issue on hand ? or does it propose a > >>>> different way of doing things completely, thereby eliminating the issue ? > >>>> > >>> Yes, the code on that web page could be a solution to the issue on > >>> hand. According to its description, the code calculates and searches > >>> URLs that may contain translations for requested page, and lists any > >>> translation that do exist. > >>> > > True, but at server expense. But how much over head does it cause? That > > will be a problem as the wiki grows in size. > > > My earlier observation about CentOS wiki's requirement on the URL of > translated pages means that the overhead is directly proportional to the > number of i18n languages registered with MoinMoin. It is constant for > every page, regardless of the size of wiki. > > Regards, > Timothy --- Err,,Timonthy I was referring to System Overhead. As in if the translation is not in the Moin cache then major overhead happens and how much depends on the the hits the Wiki recieves. What I am really doing is forecasting the future sort of. Another way to relate this is you have to allow for future growth also. As a hack the complete translate overhead can be fixed. 1. Increase moins cache. 2. Cron Job a URL fetch to each page that is known to moin. 3. Probally not the best scenario. JohnStanley