
07-18-2009, 03:27 AM
|
 |
|
|
Join Date: Aug 2008
Location: Wrocław
Posts: 1,353
Благодарил(а): 0 раз(а)
Поблагодарили:
0 раз(а) в 0 сообщениях
|
|
Quote:
Originally Posted by imported_silkroad
I have a related question.
Would it be more efficient and faster to have database tables for each translation instead of "small" and "medium" mega tables for an entire site?
We have been running this mod for just a few days, and at the current tables growth rate, our translation database will be nearly 1.2 Terrabytes in three dB tables when it is all "done and dusted" as they say, hahaha. I calculate this, perhaps incorrectly, as it seems Google has have cached around 200 pages (for each of 28 languages =~ 6000 pages) out out nearly 400Kpages, and the translation dB is currently 600MB. If we assume approximate linear growth, the full transation dB would be 400K/200 * 600 MB or 1.2 TB
I notice that our translated pages are much slower loading than the same page not in the translation dB (by quite a large factor, much slower, even though there are less MySQL queries for the translated page).
Why not put the translated pages, at least, in their own tables?
|
It wouldn't  DB has set indexes and data access is instant and constant
Translated pages will ALWAYS generate slower that not translated because first is generated normal page and after that it's translated
|