Last modified: 2014-09-09 23:53:09 UTC
I imagine this is mostly due to Firefox's JS engine, but I commonly run across articles that take an extremely long time to load the new VisualEditor interface. For example, "Domestic violence" and "Feminism" take about 30 seconds. Really long articles like "World War II" take over a minute. The interface loads in about half that time in Safari. I'm using Firefox 21.
I'm using firefox 32 and did some tests on this on en,wikipedia, and beta en, which runs HHVM, but is on a virt cluster. Article name:Barack Obama beta en: 41.7s en : 17.6s Article name: Cat beta en: 31.7s en: 16.4s Article name:Beyoncé Knowles beta en: 16.9s en: 25.4s Article name: India beta en: 36.4s en : 26.8s Article name: Richard Nixon beta en:16.2s en: 9.9s Article name:Europe beta en: 26.8s en: 28.3s Article name: English language beta en:23.7s en: 18.2 I think although it is a small test it does show the trend. The computer running this test is an i7 quad core from the 3rd gen with 8G of ram, so shouldn't be any issue on this front. Would be glad to provide any other info needed.
adding Ori for possible HHVM implications
Adding timings in chromium 37 for comparison: Article name:Barack Obama beta en: 8.1s en : 17.2s Article name: Cat beta en: 7.7s en: 16.0s Article name:Beyoncé Knowles beta en: 5.1s en: 7.5s Article name: India beta en: 4.8s en : 5.6s Article name: Richard Nixon beta en:3.6s en: 5.6s Article name:Europe beta en: 5.7s en: 7.1s Article name: English language beta en:3.5s en: 8.0s
(In reply to matanya from comment #1) > I'm using firefox 32 and did some tests on this on en,wikipedia, and beta > en, which runs HHVM, but is on a virt cluster. Comparing the time to execute of anything between beta and prod is comparing nothing of value. Different hardware, different cluster sizes (for cache, execute and db) and different code.
