Page MenuHomePhabricator

Measure the difference in performance loading large item pages and history pages before and after prefetching
Closed, ResolvedPublic

Description

Should only be done after the main parts of T254740 are done.

An idea about some tech to maybe do this with is mentioned in T258044#6311426 (jmeter)

For item loading:

  • A page with statements with 51 different properties?

For history loading:

  • A history page with summaries that refer to 51 different properties?

Rough Steps:

  • Run a version of the code without the prefetching
  • Load some pages and get timing data for full page load from the browser
  • Run a version of the code with all the prefetching
  • Load some pages and get timing data for full page load from the browser
  • Report finding here

Event Timeline

There were some helpful remarks on this topic from @Tarrow in the navigators summit:

There is the jmeter thing in the base on wikibase.git that might be useful for this. Locust (a different thing) used for termbox a bit. The dream was to have something like T230530 but we used locust on a developer laptop in the end. Detailed docs for termbox loadtesting are at: https://gerrit.wikimedia.org/r/plugins/gitiles/wikibase/termbox/+/refs/heads/master/infrastructure/load_testing/

This item could be used:

https://wikidata-federated-properties.wmflabs.org/wiki/Item:Q32

Setup with a simple maintenance script found in:

/home/toan/populateData.php on the test system

Tried out using a configured version of the mentioned locust setup but feels this is currently not viable to get any meaningful results.

Running it without prefetching against our test system with only 10 users spawning every 1 second results in very interesting behavior where the page loads eventually become to high resulting in wdqs-updater not being able to reach the website and then crashing and restarting over and over again resulting in a very random looking chart.

Ok this is new new and shiny item used for testing -> https://wikidata-federated-properties.wmflabs.org/w/index.php?title=Item:Q34

History-page: 14 seconds
Item-page: 9 seconds
Recent-changes: 10 seconds

using mod-header set X-FedProps-SourceApiResponse = 200 to skip the parser-cache.

While loading for me I now see using mod-header set X-FedProps-SourceApiResponse = 200 to skip the parser-cache.

History-page: 8 seconds
Item-page: 8 seconds
Recent-changes: 8 seconds

I believe everything is merged now, testing I get:

History-page: ~ 1 second
Item-page: less than 1 second
Recent-changes: ~ 1 second too

History-page: 1.65s
Item-page: 1.72 s
Recent-changes: 1.96,

however this is with all js and stuff. Initial page-load seems to be a bit less than 1 second on all three without parser cache.

however this is with all js and stuff. Initial page-load seems to be a bit less than 1 second on all three without parser cache.

My numbers are only counting the initial page load