| Status | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
Usage
After logging in, you can select one of the following functionalities in the menu on the left:
Applications - upload, manage and view the detailed analysis of your applications;
Schedule a Scan - launch an analysis of your source code and see jobs processes;
Rules - check a list of possible problems with its detailed description and suitable solution in order to allow a gain in energy, memory and performance.
If you are admin you can also access to:
Manage users - check and manage the users (add specific roles, check their last connection, add new users or delete existing ones);
Manage rules - check and disable the rules you don’t want anymore.
To change your user preferences or disconnect yourself from GREENSPECTOR Eclipse Plugin or GREENSPECTOR Command Line Tool, just click on your user name located on the top-right corner and select Preferences.
|
Applications
You can check the applications list and their properties. You can either edit an application by clicking on the pen or delete archive it by clicking on the trash bin folder (the pen and the trash bin folder appear when you move your cursor on the application line).
To add a new application which is not yet included in the list, just click on the button "Add an application".
If you click on one an application, you can view its detailed analysis, spanned in 4 5 tabs:
Dashboard
The Dashboard tab gives you a summary of your application’s results. You can select the version of the application by clicking in the box right next to its name.
Eco-score
The global eco-score is an indicator of your level of
ecodesign for the application. It is the average of eco-scores for the following domains :
Network, Client resources.
All eco-scores are noted between 0 and 100. To get the highest score, it is important to launch all analysisanalyses.
Two metrics are indicated with Just below the eco-score :is indicated the evolution of eco-score since the previous version of the application
.
Eco-score by domain
- Network: evaluate the level of eco-design of exchanged requests between client and server. It is calculated by analyzing the requests and their content. To get a score, it is necessary to initiate measures with the TestRunner by launch measurements either with the Power Test Cloud/Bench or with the Test Runner (and activating the
http_requestoption). Client resources: evaluate if your application is client-side resources efficient. It is calculated by the client-side resources consumption (energy, CPU, memory…). To get a score, it is necessary to initiate measures launch measurements either with the Power Test Cloud/Bench or with the TestRunner Test Runner on a PC and a smartphonedevice.
Improvements summary
This is a small bar graph summarizing the number of rules by priority. You can filter the rules in the Improvements table below by clicking on the corresponding priority. To display again all the rules, select "All the rules" in the select box on at the top right of the Improvements table.
Resources impact
This graph summarizes the impact of the your application's usage on the mobile device.
Improvements
This is the list of all the rules that were checked during analysis: rules that are correctly respected appear in green, whereas rules that are violated appear in yellow, orange or red. They are prioritized according to earnings you can get. Each rule is classified according to its domain. The number next to the domain corresponds to its eco-score.
Each rule is associated with a priority, a score and a gain.
The Priority priority is an indicator to help you to prioritize your work and is directly correlated with the gain.
The Score score is an indicator of how good the rule is verified on the application. Adding up all scores of a specific domain gives this domain’s eco-score.
The Gain gain is the difference between the maximum score and the actual score. It is correlated with the priority to help you choosing which rules you should work on at first place.
Precision 1: sometimes the gain is 0 on a static violation. The gain can indeed be very low compared to other static violations with a lot of points. This does not mean that you could not correct the violation. We are working on improving the scale of awarding points.
.
Consumed resources
Summary A summary of consumed resources for the consumed following metrics of :
: Platform Discharge, Process Data, Process Memory, Process CPU
PC url : Platform Energy
Mobile apk : Platform Discharge, Process Data, Process Memory, Process CPU
.
The difference between the last two versions of the metric is shown on the left side of the value.
Code
The following details are shown here: Code eco-score, Number of violations, Lines of code and Time Correction. Right below is the violations list. If a rule is violated, it is shown here with its priority. You can also choose to "Add an analysis", which takes you to the Scan option on the menu (explained later in this chapter).
When you click on a test case you can check its detailed analysis.
Meter
On the left menu, search and sort your test cases by
metrics. When you click on a test case you can check its detailed analysis.
Metrics
Metrics are sorted by metrics associated to the entire platform and metrics associated to a process or a thread .
Site URL metrics
Platform
Platform CPU
%
Average of CPU consumed by the platform
Platform Memory
Mo
Total of memory consumed by the platform
Platform Data
B
Total of network data exchange (in and out) by the platform
Platform Energy
Wh
Total of energy consumed by the platform
Platform Max Power
W
Maximum power consumed by the platform
Platform Discharge
Ah
Total of ampere hour consumed by the platform
Platform Discharge per second
Ah/s
Average ampere hour by second consumed by the platform
Process
Process CPU
%
Average of CPU consumed by the process
Process Memory
Mo
Average of memory consumed by the process
Process Data
B
Total of network data exchange (in and out) by the process
Process Energy
Wh
Total of energy consumed by the process
Process Discharge
Ah
Total of ampere hour consumed by the process
APK metrics
Activities
Number of current activities
Application Contexts
Number of the application contexts
Managers of in use assets
Number of resource managers used
In use assets
Number of loaded into memory resources
Death Recipients
Number of interface for receiving a callback when the process hosting has gone away.
SSL Sockets opened
Number of open SSL sockets
Loaded root views
Number of window or dialog box active for the current activity
Loaded views
Number of component inheriting the View interface loaded into memory
Rendered frames
Number of frames. This value is calculated by taking the difference of frames between the start and end of test.
Rendered frames with slow loading
Number of frames putting more than 16ms to charge. This value is calculated by taking the difference of frames between the start and end of the test.
Evolution
In the evolution tab you can compare on a graphic the average measures result by versions. On the test cases list, you can check their detailed analysis between two versions.
Schedule a Test
Rules
For each tab (Android, CSS, HTML, Java and PHP) you can use the search tool in order to filter the rules by language. Each rule has its Energy Gain, Memory Gain, Performance and Difficulty.
Manage users
This option on the menu on the left lets youYou can verify the stability of your measures (more details here).
Test Results
You will find the results of your functional tests (passed or failed).
Budgets
You have the possibility to configure budgets in order to better analyze and monitor the quality of your application: the page Configure the budgets issues in more detail this feature.
Evolution
In the evolution tab you can compare on a graphic the average measures result by versions. On the test case list, you can check their detailed analysis between two versions.
Benchmark
This tab allows you to launch benchmark tests.
- Select your application: the name of an application which is already created in GREENSPECTOR. You can also add an application by clicking on Add an application.
- Version: the version of the application version which is already created in GREENSPECTOR. You can also add a version by clicking on Add a version.
- Select the environment for the test: choose one of the available devices on the Power Test Cloud (or in your Power Test Bench).
- Website or Mobile app: select whether you want to test a website or a mobile Android application.
- URL: an URL pointing to the website or the APK you want to test.
- Iterations: number of executions of the tests.
- Chrome or Firefox : select the browser on which to run the measures in case you are testing a website.
Tests tracking
This tab lists all the tests you have launched.
- Pending: jobs that are in pending state (device not available).
- Running: jobs in progress.
- Finished: jobs that are done.
Once finished, several information on the finished list are available:
- Ended at: date and time at which the test was finished.
- Status: failed or finished, in case of a failure, fly over the exclamation mark icon to get more details.
- Tests Passed: status of the functionnal tests.
Modules
Find here all the GREENSPECTOR modules you can download.
Rules
Here, more detailed information about software ecodesign good practices. Rules are organised in 3 domains: code, network and client resources. For the code domain, you can also filter the rules by language.
Each rule includes an estimate of potential gains in energy, memory, performance, as well as an indication of the difficulty to apply it.
Administration
Test times
| Status | ||||||
|---|---|---|---|---|---|---|
|
License
| Status | ||||||
|---|---|---|---|---|---|---|
|
Users
This option on the left menu bar allows you to manage the current users, add a new one or delete a current one.
...
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|