Our users are complaining that the New Editor performance is slower than the current Editor. It is especially slow in loading the Editor page or any pop-up windows. It is also slow in saving changes. Could you please improve?
13 comments
-
Mikaël Hell Official comment Hi Demizu,
Our development team are working on the speed problem, the first internal feedback are really encouraging.
I will give more information when the modifications are available or a release scheduled
Kind regards
Mikael -
Inge Lever Dear Mikaël,
Great that this is being solved. Our users are also complaining that the new editor is very slow.
Kind regards,
Inge
-
Mikaël Hell Hello Inge and Sachiyo,
The last release contains the last speed optimisations (first optimisation step), can you confirm me that it is better now ?
If it is ok for you, can I close this issue ?
Best regards,
Mikael -
Inge Lever Dear Mikaël,
I will aks our translators to try the new editor again and tell us whether the speed has improved and will let you know.
Kind regards,
Inge
-
Mikaël Hell Thanks a lot Inge,
I hope that your user feedbacks will be positive
Mikael -
Inge Lever Dear Mikaël,
One of our translators just let me know he thinks it is indeed working a bit smoother and faster :-)
Although he noticed that sometimes the editor get's stuck while “Processing… please stand by”. The only solution was to refresh the whole page again.
He had some other comments too for which I will open new tickets later today ;-)
Kind regards,
Inge
-
Mikaël Hell Great news. We are happy that the speed optimization was benefic for your users.
If the "Processing… please stand by” do not disappear can you open the developer tool (press F12 and your keyboard) and send us a screenshot of the "Console" tab.I am waiting for your next feedbacks ;-P
Mikael -
Andrew Jones Hi, This still is an issue for us. It takes a long time for the new editor window to open (much longer than the old one), and the filter operation is also very slow. The first is not so bad, but we use filters a lot and so we would like it addressed.
-
Alexandre Ronin Hi Andrew,
We're sorry to hear that you still feel that your experience with the editor is slow. Rest assured that speed and optimization issues are our number one priority, and we're constantly monitoring ways we can improve the editor in this regard. For instance, we're pushing an update soon that caused the editor to slow down significantly over time when navigating through segments. This will already likely help your situation.
Let's still try and pinpoint the source of your problems together. As far as I can tell from your message, the slowness seems to come from fetching segments and displaying them on your browser window. Our tests show that the time to fetch segments is actually faster in the new translation editor. However, due to the complexities of the new systems when displaying segments, this can cause slowdowns when computing the data and displaying everything on screen. The limiting factor here is the computing power of your PC
This is generally not an issue, but it can start to be a problem when displaying over 50 segments per page. Could you please confirm how many segments you're displaying per page?
Thank you very much for sharing your feedback. We hope to resolve your situation very soon.
Kind regards,
Alex
-
Andrew Jones Wojciech asked for two screenshots, of Console and Network tabs. That page seems to have disappeared, but I've attached them.
-
Andrew Jones The speed issue seems now just with loading the editor itself--about 40 seconds. Segment to segment is fairly quick.
-
Andrew Jones I've just spent 10 min waiting for each page to load in the new editor. It takes about 5 sec in the old one. This is a common issue for us, and so most are not switching to the new editor.
-
Linquake team I can confirm that we're experiencing some serious perfomance issues with the new editor also. Especially when bigger documents are involved, loading new pages takes dozens of minutes.
I'm pushing our project managers to use the new editor, but they are stll very reluctant because of this issue.
Kind regards,
Pieter Cramer