New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 884146 link

Starred by 1 user
Status: Fixed
Owner:
perezju@chromium.org
Closed: Dec 18
Cc:
sullivan@google.com
simonhatch@chromium.org
█ nednguyen@chromium.org
dtu@chromium.org
█ picksi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

Update memory benchmarks doc

Project Member Reported by perezju@chromium.org, Sep 14 
The doc here:
https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

Should now mention:
- The possibility of using pinpoint to run try jobs.
- The existence of --story-tag-filter health_check to run a smaller (but still representative) subset of the stories.

Comment 1 by perezju@chromium.org, Dec 17

Cc: dtu@chromium.org
Components: Internals>Instrumentation>Memory
Project Member

Comment 2 by bugdroid1@chromium.org, Dec 18 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9e50ddde6164143cdb30ce44aca7f2ef401486e2

commit 9e50ddde6164143cdb30ce44aca7f2ef401486e2
Author: Juan Antonio Navarro Perez <perezju@chromium.org>
Date: Tue Dec 18 10:22:49 2018

[docs] Update memory-infra/memory_benchmarks on pinpoint jobs

Remove reference to no longer existing `run_benchmark try` command, and
describe pinpoint try jobs instead.

Bug:  884146 
Change-Id: I95370496463b1adfe046c3bf48d3923e18831bf9
Reviewed-on: https://chromium-review.googlesource.com/c/1349322
Reviewed-by: Dave Tu <dtu@chromium.org>
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617433}
[modify] https://crrev.com/9e50ddde6164143cdb30ce44aca7f2ef401486e2/docs/memory-infra/memory_benchmarks.md

Comment 3 by perezju@chromium.org, Dec 18

Status: Fixed (was: Assigned)
►

Sign in to add a comment