Why does Polyspace Dashboard not show any project or takes very long to load the data in Polyspace Code Prover R2016b?

Sometimes when opening Polyspace Web Metrics (Dashboard) it takes many minutes before the projects are shown. This often happens in the morning after several hundred analyzes have been run during the night.

Sometimes Polyspace Web Metrics does not show any projects. Then only a restart of the polyspaced service helps.

What is the issue here and how can it be avoided?

Answer 1

[MathWorks Support Team]

Regarding the fact that it sometimes takes a long time, it depends on when the page has been loaded and if Polyspace web metrics is populating metrics statistics.

Now, there are two thresholds to set depending on the volume inside the database. These can influence data to collect and to display:

1. Maximum number of projects
2. For each project, there is the From/To which displays statistics on all the runs between this interval

There is no concrete number defining the "allowed" number of projects/runs on the Web Metrics dashboard, but here are a few things to consider:

• The important factor is the total number of managed runs, regardless of the total number of projects.
• This possible maximum number also depends on the performance of the machine running the Metrics Server.
• Old runs should be removed from projects.
• Usually for an ongoing project, it should be sufficient to keep no more than about 15 runs.
• It is possible to set up multiple metrics servers (no additional license is needed). For example, you could have a metrics server for the daily work on the ongoing projects, and another one for archiving the already completed projects.
• Besides that, it might be necessary to clean up the jobs in the queue manager (now called the Job Monitor). There, completed jobs should be deleted if they are useless, or downloaded if they are not. The Job Monitor is not a repository. It's better not to have too much jobs on it. Cleaning the job monitor is easy: select the useless jobs, then right-click and choose "Remove from queue".

If the above hints do not help, please contact MathWorks Technical Support with a summary of outcomes of the mentioned attempts. Please also provide the following files for further investigation (located by default in C:\PolySpace\PolySpace_RLDatas or in %APPDATA%\Polyspace_RLDatas):

1. polyspaced.log file
2. PolyspaceMetrics.log file
3. The Metrics database results-repository.db. The default path of this file under Windows is: "C:\Polyspace\Polyspace_RLDatas\results-repository\results-repository.db" (it contains only the structure of the repository).