PDash 2.0

Bug #1053005 reported by Dana Florescu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zorba
New
Critical
Chris Hillery

Bug Description

Functionality-wise, the general idea is to have a web-based interface to administer and configure the site. The two two most urgent and important capabilities I would like to have are

1. Be able to set the default baseline for each test, and
2. Be able to set the default starting date from which data is going to be displayed.

Other nice-to-haves are:

3. Be able to add/remove tests
4. Set the default number of times each test is going to be run (and remove this number from the name of the test).
5. Thin-out history, e.g. say for a particular period of time I want only 1 out of each 5 data point to be displayed.

It would be cool if all these config settings were on a per-user basis, but I think think this is something we should sweat too much about.

Another wish is to have a dedicated machine to run the tests, or at least make sure that while the tests are run, nothing else is running on that machine.

---

Mauro did a proposed "PDash 2.0" some time ago, but it is unclear whether that had any infrastructure or other significant improvements from what is run today.

Changed in zorba:
importance: Undecided → Critical
assignee: nobody → Sorin Marian Nasoi (sorin.marian.nasoi)
milestone: none → 3.0
Chris Hillery (ceejatec)
description: updated
summary: - release PDash 2.0
+ PDash 2.0
Revision history for this message
Markos Zaharioudakis (markos-za) wrote :

A correction:

It would be cool if all these config settings were on a per-user basis, but I think think this is something we should NOT sweat too much about.

Revision history for this message
Markos Zaharioudakis (markos-za) wrote :

2 more wishes:

6. Send an email if preformance regresses more than X% from the baseline, where the default value of X is settable via the web admin interface. I think it makes most sense if the email is sent to me only.

7. The current web site is rather slow. Each click takes at least a few seconds. It would be nice if this was fixed.

tags: added: new-functionality-requirement
tags: added: performance-problem
Changed in zorba:
assignee: Sorin Marian Nasoi (sorin.marian.nasoi) → Chris Hillery (ceejatec)
Revision history for this message
Chris Hillery (ceejatec) wrote :

Note from our meeting on June 3:

Perf testing
  1. Get santacruz running nightly perf queries again
  2. Post data to new 28.io project (based on mongohq)
  3. Write JSONiq queries to massage data (checking against baselines
  if necessary, etc)
  4. Set up Metric Insights or similar account to load data for vis
  5. Set up alerts to Markos when data exceeds certain thresholds
  6. Markos will assess problems, file bugs/solve problems, and reset
  baselines

I do not currently believe this will be complete by Zorba 3.0, but I'm leaving the milestone there in case.

Changed in zorba:
milestone: 3.0 → none
milestone: none → 3.0
Chris Hillery (ceejatec)
Changed in zorba:
milestone: 3.0 → 3.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.