@@ -64,15 +64,20 @@ A few observations:
64
64
65
65
## Memory usage:
66
66
67
- | rules set | boreal | yara |
68
- | -------------- | ---- | ---- |
69
- | orion | 12.8 MB | 12.3MB |
70
- | atr | 12.6 MB | 14.0MB |
71
- | reversinglabs | 14.9 MB | 15.8MB |
72
- | panopticon | 10.9 MB | 13.4MB |
73
- | c0ffee | 22.9 MB | 200MB |
74
- | icewater | 77.9 MB | 55.1MB |
75
- | signature-base | 78.9 MB | 27.8MB |
67
+ In ` boreal ` , different compiler profiles can be used, with one prioritizing scanning speed,
68
+ and the other one prioritzing memory usage. Those two profiles are presented separately to
69
+ show the memory consumption impact.
70
+
71
+ | rules set | boreal (speed) | boreal (memory) | yara |
72
+ | -------------- | -------------- | --------------- | ------- |
73
+ | orion | 10.9 MB | 9.71 MB | 14.8 MB |
74
+ | atr | 10.7 MB | 8.53 MB | 15.7 MB |
75
+ | reversinglabs | 13.6 MB | 12.2 MB | 17.7 MB |
76
+ | panopticon | 9.07 MB | 7.71 MB | 15.3 MB |
77
+ | c0ffee | 16.7 MB | 13.4 MB | 198 MB |
78
+ | icewater | 61.6 MB | 55.6 MB | 56.3 MB |
79
+ | signature-base | 70.3 MB | 44.2 MB | 35.5 MB |
80
+ | yara-rules | 99.3 MB | 74.0 MB | 45.4 MB |
76
81
77
82
Note that optimizing memory usage has not been a priority for the moment, as the focus was
78
83
on optimizing performances. However, the next release will provide a way to proritize
0 commit comments