I have followed the guide:
https://forum.proxmox.com/threads/how-to-integrate-eset-antivirus-with-pmg.49788/post-232199
https://forum.proxmox.com/threads/pmg-6-1-how-to-add-antivirus.67006/#post-320192
Since implementing ESET, my average processing time has almost tripled on the same hardware:
Based on @Stoiko Ivanov , the third is "CustomCheckscripts".
If you have implemented ESET, have you had the same impact on the 3rd time or were you able to reduce the times?
System performance appears good:
https://forum.proxmox.com/threads/how-to-integrate-eset-antivirus-with-pmg.49788/post-232199
https://forum.proxmox.com/threads/pmg-6-1-how-to-add-antivirus.67006/#post-320192
Since implementing ESET, my average processing time has almost tripled on the same hardware:
Code:
BEFORE (ClamAV only)
Mar 5 10:59:45 spam pmg-smtp-filter[114537]: 1A089D6222A7EE02F73: processing time: 3.182 seconds (3.037, 0.106, 0)
Mar 5 10:59:50 spam pmg-smtp-filter[114668]: 1A004A6222A7F2BFD92: processing time: 3.564 seconds (3.436, 0.088, 0)
Mar 5 10:59:43 spam pmg-smtp-filter[114376]: 1A004A6222A7ECB1EF9: processing time: 2.952 seconds (2.837, 0.046, 0)
Mar 5 10:58:55 spam pmg-smtp-filter[114537]: 1A004A6222A7BCA585D: processing time: 3.126 seconds (2.958, 0.1, 0)
Mar 5 10:58:18 spam pmg-smtp-filter[114537]: 1A004A6222A799F3488: processing time: 0.892 seconds (0.769, 0.056, 0)
Mar 5 10:51:28 spam pmg-smtp-filter[114482]: 1A004A6222A5FA3FBD8: processing time: 6.077 seconds (5.882, 0.128, 0)
Mar 5 10:44:59 spam pmg-smtp-filter[114335]: 1A06A36222A4783E140: processing time: 2.78 seconds (2.659, 0.046, 0)
Mar 5 10:44:16 spam pmg-smtp-filter[114035]: 1A06A36222A44C0EA7E: processing time: 4.465 seconds (4.333, 0.059, 0)
Mar 5 10:44:09 spam pmg-smtp-filter[114267]: 1A06A36222A4470A0E6: processing time: 2.443 seconds (2.408, 0.023, 0)
AFTER ESET (and ClamAV still active)
Mar 5 17:35:21 spam pmg-smtp-filter[9827]: 1A09446223049C47665: processing time: 13.116 seconds (7.383, 0.024, 5.689)
Mar 5 17:32:54 spam pmg-smtp-filter[10063]: 1A09446223040C22C4B: processing time: 10.471 seconds (4.626, 0.093, 5.722)
Mar 5 17:31:15 spam pmg-smtp-filter[9827]: 1A0944622303A41146B: processing time: 15.497 seconds (9.655, 0.102, 5.711)
Mar 5 17:30:14 spam pmg-smtp-filter[10063]: 1A09446223036C12093: processing time: 9.945 seconds (3.83, 0.094, 5.99)
Mar 5 17:30:14 spam pmg-smtp-filter[10063]: 1A09446223036C12093: processing time: 9.945 seconds (3.83, 0.094, 5.99)
Mar 5 17:25:54 spam pmg-smtp-filter[9827]: 1A09446223025BCEC27: processing time: 21.84 seconds (6.778, 7.307, 6.426)
Mar 5 17:22:35 spam pmg-smtp-filter[10063]: 1A0944622301A2ADEC3: processing time: 8.886 seconds (3.032, 0.051, 5.775)
Mar 5 17:15:07 spam pmg-smtp-filter[9827]: 1A09446222FFE020757: processing time: 11.169 seconds (2.945, 0.022, 6.79)
Mar 5 17:04:07 spam pmg-smtp-filter[9658]: 1A09446222FD4C7E0DD: processing time: 11.406 seconds (5.504, 0.134, 5.716)
Based on @Stoiko Ivanov , the third is "CustomCheckscripts".
If you have implemented ESET, have you had the same impact on the 3rd time or were you able to reduce the times?
System performance appears good:
Code:
root@spam:/tmp# dig proxmox.com
; <<>> DiG 9.16.22-Debian <<>> proxmox.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52857
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;proxmox.com. IN A
;; ANSWER SECTION:
proxmox.com. 2719 IN A 212.224.123.69
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Mar 05 17:46:25 AEDT 2022
;; MSG SIZE rcvd: 56
root@spam:/tmp# pmgperf /
CPU BOGOMIPS: 47884.56
REGEX/SECOND: 1359465
HD SIZE: 104.57 GB (/dev/mapper/pmg-root)
BUFFERED READS: 266.57 MB/sec
AVERAGE SEEK TIME: 3.03 ms
FSYNCS/SECOND: 1054.84
DNS EXT: 125.73 ms
DNS INT: 4.90 ms (domain.com)