Problem with GS Cloud TM fuzzy matching and with Performance and Tuning feature

Hello,

Yesterday, I started a project using a GS Cloud TM (+60,500 TUs). As I usually do, I pre-translated the files (using a 70% match threshold) and then I started translating. To my surprise, when I went to some segments that had been pre-translated as fuzzy matches, I saw no matches at all on the Translation Results pane (whereas I DO know that there is a fuzzy match stored in the TM), so I could not see graphically how did the new string differ from that stored in the TM.

Since yesterday (as it unfortunately happens every week with GS Cloud TMs) GroupShare was not working properly, I did not give it much thought. Yet, a moment later, GS was apparently fully operative again and I still had the same issue with another fuzzy match. I thought that perhaps there was a performance problem with the TM, and on the relevant TM Settings > Performance and Tuning dialogue I found that, apparently, TM needed some statistics' recomputing, since they had never been updated and "because the translation memoriy has significantly grown in size".

Since I do know that recomputing and re-indexing actions can take quite a while (and there is no way to see how long will they take), I left it for the end of the day and clicked on the Recompute Fuzzy Index Statistics... button when I called it a day, expecting to see the TM statistics updated by today morning...

...Yet, again to my surprise, when I switched on my computer's monitor, I saw that after a +8 hours span, the statistics where STILL being recomputed. This TM has already attained a certain size (as previously stated, above 60,500 TUs), but I honestly doubt updating the stats of a memory of such size takes more than 8 hours. Obviously, I cancelled the task, but the problem with fuzzy matches is still present :(. The most shocking thing is that this is not a constant issue: sometimes TM recognizes the fuzzy matches and sometimes, it does not (and I repeat: all fuzzy matches had been obtained via pre-translation and I confirmed in all instances that such matches are stored in the TM).

Has anyone experienced a similar problem? Since GroupShare performance is less than optimal, I do not know if this is a problem with Studio or with GS and apparently I cannot solve the issue with the tools that Studio provides :(.

Any help would be much appreciated :).

Thank you!