Update README to feature the full version of Trace Analyzer
This commit is contained in:
15
README.md
15
README.md
@@ -18,6 +18,7 @@ If you decide to use DRAMSys in your research please cite the paper [2] or [3].
|
||||
## Included Features
|
||||
|
||||
- **Standalone** simulator with trace players and traffic generators or **TLM-2.0-compliant library**
|
||||
- **Trace Analyzer** for visual and metric-based result analysis
|
||||
- Coupling to **gem5** supported
|
||||
- Cycle-accurate **DDR3/4**, **LPDDR4**, **Wide I/O 1/2**, **GDDR5/5X/6** and **HBM1/2** modelling
|
||||
- Bit-granular address mapping with optional XOR connections [7]
|
||||
@@ -31,7 +32,7 @@ If you decide to use DRAMSys in your research please cite the paper [2] or [3].
|
||||
## Additional Features
|
||||
|
||||
- Cycle-accurate **DDR5**, **LPDDR5** and **HBM3** modelling
|
||||
- **Trace Analyzer** for visual and metric-based result analysis
|
||||
- Extended analysis features for the **Trace Analyzer**
|
||||
- **Free academic** or **commercial** licenses available (please contact [Matthias Jung](mailto:matthias.jung@iese.fraunhofer.de) for more information)
|
||||
|
||||
## Video
|
||||
@@ -48,7 +49,15 @@ All requests, responses and DRAM commands can be recorded in an SQLite trace dat
|
||||
|
||||
The Trace Analyzer's main window is shown below.
|
||||
|
||||
If you are interested in the Trace Analyzer, if you need support with the setup of DRAMSys in a virtual platform of your company, or if you require custom modifications of the simulator please contact [Matthias Jung](mailto:matthias.jung@iese.fraunhofer.de).
|
||||
A basic version of Trace Analyzer is included in the open source release of DRAMSys.
|
||||
However, the full version of the Trace Analyzer includes many additional analysis features:
|
||||
- Detailed transaction-level latency analysis
|
||||
- Power, bandwidth, and buffer utilization analysis over simulation time intervals
|
||||
- Timing dependency analysis at the DRAM command level
|
||||
- Calculation of numerous predefined and user-defined metrics
|
||||
- VCD export of generated trace
|
||||
|
||||
If you are interested in the full version of Trace Analyzer, if you need support with the setup of DRAMSys in a virtual platform of your company, or if you require custom modifications of the simulator please contact [Matthias Jung](mailto:matthias.jung@iese.fraunhofer.de).
|
||||
|
||||

|
||||
|
||||
@@ -58,7 +67,7 @@ To use DRAMSys, first clone the repository.
|
||||
|
||||
### Dependencies
|
||||
|
||||
DRAMSys requires a **C++17** compiler. The build process is based on **CMake** (minimum version **3.24**). Furthermore, the simulator is based on **SystemC**. SystemC is included with FetchContent and will be build automatically with the project. If you want to use a preinstalled SystemC version, export the environment variable `SYSTEMC_HOME` (SystemC installation directory) and set the CMake option `DRAMSYS_USE_EXTERNAL_SYSTEMC`. Also make sure that the SystemC library was built with the same C++ version.
|
||||
DRAMSys requires a **C++17** compiler. The build process is based on **CMake** (minimum version **3.24**). Furthermore, the simulator is based on **SystemC**. SystemC is included with FetchContent and will be build automatically with the project. If you want to use a preinstalled SystemC version, export the environment variable `SYSTEMC_HOME` (SystemC installation directory) and enable the `DRAMSYS_USE_EXTERNAL_SYSTEMC` CMake option. Also make sure that the SystemC library was built with the same C++ version.
|
||||
|
||||
### Building DRAMSys
|
||||
|
||||
|
||||
Reference in New Issue
Block a user