Skip to content

Commit cfb0ffe

Browse files
authored
Merge pull request #187761 from ronhogue/master
Overview and Priming updates
2 parents 2af84a3 + a4facce commit cfb0ffe

File tree

2 files changed

+33
-10
lines changed

2 files changed

+33
-10
lines changed

articles/hpc-cache/hpc-cache-overview.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Describes Azure HPC Cache, a file access accelerator solution for h
44
author: ronhogue
55
ms.service: hpc-cache
66
ms.topic: overview
7-
ms.date: 01/19/2022
7+
ms.date: 02/03/2022
88
ms.author: rohogue
99
---
1010

@@ -42,6 +42,18 @@ A research institute that wants to port its genomic analysis workflows into Azur
4242

4343
Azure HPC Cache also can be leveraged to improve efficiency in tasks like secondary analysis, pharmacological simulation, or AI-driven image analysis.
4444

45+
### Silicon design verification
46+
47+
The silicon design industry’s design verification workloads, known as “electronic design automation (EDA) tools” are compute-intensive tools that can be run on large-scale virtual machine compute grids.
48+
49+
Azure HPC Cache can provide on-cloud caching of design data, libraries, binaries, and rule database files from on-premises storage systems. This provides local-like response times for directory listings, metadata, and data reads, and eliminates the need for complex data migration, syncing, and copying operations.
50+
51+
Azure HPC Cache also can be set up to cache output files being written by the compute jobs. This configuration gives immediate acknowledgement to the compute workflow and subsequently writes the changes back to the on-premises NAS.
52+
53+
HPC Cache allows chip designers to scale EDA verification jobs to tens of thousands of cores with ease, and pay minimal attention to storage performance.
54+
55+
Learn more about [High-performance computing for silicon](https://azure.microsoft.com/solutions/high-performance-computing/silicon/)
56+
4557
### Financial services analytics
4658

4759
An Azure HPC Cache deployment can help speed up quantitative analysis calculations, risk analysis workloads, and Monte Carlo simulations to give financial services companies better insight to make strategic decisions.

articles/hpc-cache/prime-cache.md

Lines changed: 20 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use the cache priming feature (preview) to populate or preload cach
44
author: ronhogue
55
ms.service: hpc-cache
66
ms.topic: how-to
7-
ms.date: 01/26/2022
7+
ms.date: 02/03/2022
88
ms.author: rohogue
99
---
1010

@@ -47,7 +47,9 @@ In the manifest, specify the namespace path to the directories or files that you
4747
"config": {
4848
"cache_mode": "0",
4949
"maxreadsize": "0",
50-
"resolve_symlink": "0"
50+
"resolve_symlink": "0",
51+
"threads":"8",
52+
"skip_estimation":"0"
5153
},
5254

5355
"files": [
@@ -75,14 +77,17 @@ In the manifest, specify the namespace path to the directories or files that you
7577

7678
There are three sections to the priming manifest file:
7779

78-
* `config` - settings for the priming job
79-
* `files` - individual files that will be pre-loaded
80-
* `directories` - file paths that will be pre-loaded
81-
* `include` and `exclude` - regular expression strings that modify the directory priming task
80+
* Configuration (`config`) - settings for the priming job
81+
* File and directory statements:
82+
83+
* `files` - individual files that will be pre-loaded
84+
* `directories` - file paths that will be pre-loaded
85+
86+
* Global include and exclude statements (`include` and `exclude`) - regular expression strings that modify the directory priming task
8287

8388
### Configuration settings
8489

85-
There are three settings in the `config` section of the manifest file:
90+
The `config` section of the manifest file sets these parameters:
8691

8792
* Cache mode - Sets the behavior of the priming job. Options are:
8893

@@ -92,7 +97,11 @@ There are three settings in the `config` section of the manifest file:
9297

9398
* `maxreadsize` - Sets the maximum number of bytes that will be pre-loaded per file. Leave this set to 0 (the default) to always load the entire file regardless of size.
9499

95-
* `resolve_symlink` - Set this to true (`1`) if you want to resolve symbolic links when priming. If `resolve_symlink` is enabled, symbolic link targets are pre-loaded entirely, regardless of include and exclude rules.
100+
* `resolve_symlink` - Set this to true (1) if you want to resolve symbolic links when priming. If `resolve_symlink` is enabled, symbolic link targets are pre-loaded entirely, regardless of include and exclude rules.
101+
102+
* `threads` - The number of priming threads to use. Valid values are 1 to 128. The default value is 8, to balance between priming and servicing client requests.
103+
104+
* `skip_estimation` - Before it starts copying files, the priming job runs an estimate of the amount of data to be primed. Set the `skip_estimation` flag to true (1) if you want to move directly to the file priming phase. If you skip the estimation phase, the progress report might be less accurate. The default value is 0, to include the estimation phase.
96105

97106
### File and directory paths
98107

@@ -195,7 +204,9 @@ Priming jobs are listed in the **Prime cache** page in the Azure portal.
195204

196205
![screenshot of the priming jobs list in the portal, with jobs in various states (running, paused, and success). The cursor has clicked the ... symbol at the right side of one job's row, and a context menu shows options to pause or resume.](media/prime-cache-list.png)
197206

198-
This page shows each job's name, its state, its current status, and summary statistics about the priming progress. The summary in the **Details** column updates periodically as the job progresses.
207+
This page shows each job's name, its state, its current status, and summary statistics about the priming progress. The summary in the **Details** column updates periodically as the job progresses. The **Status** field is populated when a priming job starts; this field also gives basic error information like **Invalid manifest** if a problem occurs.
208+
209+
Before a priming job starts, it has the state **Queued**. Its **Status** and **Details** fields are empty.
199210

200211
Click the **...** section at the right of the table to pause or resume a priming job.
201212

0 commit comments

Comments
 (0)