Michael added a comment.

  Ok, so the patch from yesterday that added some primitive performance 
logging, did provide some insights:
  
  Search for `0: test started` in yesterday's logs 
<https://integration.wikimedia.org/ci/job/selenium-daily-beta-WikibaseLexeme/1193/console>
 to find the output for the test we wanted to look at closer 
<https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseLexeme/+/736496/5/tests/selenium/specs/form.edit.js>.
  
  Some observations:
  
  - Creating a new Item via the API takes around 10 seconds
  - Creating a new Lexeme via the API takes around 20 seconds
  
  The latter point I confirmed via the API Sandbox on beta wikidata:
  
  F34731312: image.png <https://phabricator.wikimedia.org/F34731312>
  
  It is unclear why it takes such unreasonable amounts of time. Interestingly, 
creating the Lexeme via the API is much faster! Though, it is no surprise now 
that we are seeing a lot of timeout errors in our daily Lexeme Browser tests.
  
  I'm not yet sure how to debug this further. Is it possible to somehow profile 
requests on //beta//?
  
  ----
  
  There is also a failing test around login problems that is unrelated to 
timeouts. I'm still looking into that one.

TASK DETAIL
  https://phabricator.wikimedia.org/T277862

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Michael
Cc: noarave, Pablo-WMDE, toan, Sahilgrewalhere, Lucas_Werkmeister_WMDE, 
zeljkofilipin, WMDE-leszek, Michael, Ladsgroup, Tarrow, hoo, Addshore, 786, 
Suran38, Biggs657, Invadibot, Lalamarie69, maantietaja, Juan90264, Alter-paule, 
Hazizibinmahdi, Beast1978, Un1tY, Akuckartz, Hook696, Kent7301, joker88john, 
CucyNoiD, Nandana, Gaboe420, Giuliamocci, Cpaulf30, Lahi, Gq86, Af420, 
Bsandipan, GoranSMilovanovic, Mahir256, QZanden, LawExplorer, Lewizho99, 
Maathavan, _jensen, rosalieper, Bodhisattwa, Scott_WUaS, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331
_______________________________________________
Wikidata-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to