| Excerpt |
|---|
|
The definition and sample files used by ecCodes engine to decode all kind of messages can be built into the library (embedded) providing a performance improvement by significantly reducing access to the filesystem |
Step-by-step guide
The definition and sample files used by ecCodes engine to decode all kind of messages can be built into the library (embedded) providing a performance improvement by significantly reducing access to the filesystem.
This feature is called MEMFS (MEMory FileSystem) and can be enabled at configuration time (when you invoke cmake) by:
| Code Block |
|---|
% cmake /path/to/src -DENABLE_MEMFS=ON |
This will take longer to compile and the resulting library will be larger but whenever a definition file (*.def or *.table) or a sample file (*.tmpl) is accessed, its contents will be fetched from memory and no access to the file system will be made.
If you invoke the codes_info tool with this configuration, the paths reported will contain the prefix "/MEMFS/".
For example:
| Code Block |
|---|
% codes_info
...
Default definition files path is used: /MEMFS/definitions
...
Default SAMPLES path is used: /MEMFS/samples |
| Note |
|---|
Please note that once ecCodes is built in this mode, any subsequent changes to the installed definition/sample files will NOT be picked up |
Related articles
| Content by Label |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | ~usa |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ("kb-how-to-article","eccbufr-faqs","bufr","grib","definitions","memory","performance") and type = "page" and space = "UDOC" |
|---|
| labels | kb-how-to-article |
|---|
|