Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mean transaction time discrepancy between the Transaction overview and details pages in the console #94396

Closed
kevin-v-ngo opened this issue Dec 28, 2022 · 3 comments
Assignees
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@kevin-v-ngo
Copy link

kevin-v-ngo commented Dec 28, 2022

There is a discrepancy between the Transaction time on the Transaction fingerprint overview page and the Transaction fingerprint details page.

Loom video for context.

Jira issue: CRDB-22871

@kevin-v-ngo kevin-v-ngo added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Dec 28, 2022
@koorosh koorosh self-assigned this May 30, 2023
@koorosh
Copy link
Collaborator

koorosh commented Jun 19, 2023

In 23.1.0 version, new data requested on navigation from Transactions page to Transaction details page.
It's probably causes this mismatch for transaction fingerprints during workload.

Now, for most recent versions, this behaviour is changed:

  • navigating to Transaction details page doesn't request updated data;
  • navigation from Transaction details back to Transactions page would still request new data.

@dongniwang , currently it is possible for users to disable auto-refresh on pages,
but when user navigates between pages, we still re-request new data.
Does it make sense to show users stale (last received) data even after navigation
between pages (with disabled auto-refresh? What do you think?

@koorosh
Copy link
Collaborator

koorosh commented Jun 26, 2023

Better visibility of whether data is changed on transaction page (after navigation back on it) is done in scope
of #105157

@koorosh
Copy link
Collaborator

koorosh commented Jun 26, 2023

I'm in favor to close this issue as there's no mismatches of data shown on pages but unintended requests for new data and lack of visibility when new data is fetched (which is already done by mentioned PR above).

@koorosh koorosh closed this as completed Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

No branches or pull requests

2 participants