Make WordPress Core

Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#43315 closed enhancement (fixed)

Add timer start to SAVEQUERIES data

Reported by: rarst's profile Rarst Owned by: johnbillion's profile johnbillion
Milestone: 5.1 Priority: normal
Severity: normal Version:
Component: Database Keywords: has-dev-note
Focuses: performance Cc:

Description

Currently $wpdb->queries will capture elapsed query times, but lacks the start time point for each query.

Adding this data will be helpful for performance tools to determine the distribution of queries in a page load and to correlate queries with containing operations.

Attachments (1)

Added_time_start_to_SAVEQUERIES_data_.patch (591 bytes) - added by Rarst 6 years ago.

Download all attachments as: .zip

Change History (11)

#1 @Rarst
6 years ago

  • Keywords has-patch added

#2 @SergeyBiryukov
6 years ago

  • Milestone changed from Awaiting Review to 5.0

#3 @johnbillion
6 years ago

  • Owner set to johnbillion
  • Status changed from new to reviewing
  • Version trunk deleted

#4 @johnbillion
6 years ago

  • Resolution set to fixed
  • Status changed from reviewing to closed

In 42789:

Database: Add the query start time to logged query data.

This allows debugging plugins to plot the time at which queries were executed.

Props Rarst for initial patch.

Fixes #43315

#5 @johnbillion
5 years ago

  • Keywords needs-patch added; has-patch removed
  • Milestone changed from 5.0 to 5.0.1
  • Resolution fixed deleted
  • Status changed from closed to reopened

@since needs updating

#6 @pento
5 years ago

  • Milestone changed from 5.0.1 to 5.0.2

#7 @pento
5 years ago

  • Milestone changed from 5.0.2 to 5.0.3

#8 @SergeyBiryukov
5 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In 44345:

Docs: Update @since tag for the addition of query start time to logged query data.

Fixes #43315.

#9 @desrosj
5 years ago

  • Keywords needs-patch removed
  • Milestone changed from 5.0.3 to 5.1

This does not appear to have been backported to the 5.0 branch, so updating the milestone to be correct.

Note: See TracTickets for help on using tickets.