Issue 101: Improve performance of fuzzy pinyin in ibus-pinyin engine http://code.google.com/p/ibus/issues/detail?id=101
Comment #2 by hashao2: All the phrase and char should be put into a table with a unique key: ID | word | freq Phrases or chars with the same input keyset should be put in a single row and use the ID from the phrase table. Since everytime you search the same key, you want to fetch back all the words with the same input keyset anway. Everyrow might also have an unique id. pinyinID | k1 | k2 | k3 | k4 | ID1,ID2,ID3 That way, when set a new fuzzy input rule, just build a new fuzzy table corresponding to the right pinyinID or Phrase ID, depend on your taste: k1 | k2 | k3 | k4 | ID1,ID2,ID3... or someway to joint the 2 table. This will shorten the Pinyin table greatly. If this is still too slow, you can eliminate the phrase table and put the data directly into where ID1,ID2,ID3... were as: phrase1:freq,phrase2:freq,phrase3:freq -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ibus-devel" group. iBus project web page: http://code.google.com/p/ibus/ iBus dev group: http://groups.google.com/group/ibus-devel?hl=en -~----------~----~----~----~------~----~------~--~---
