Hello world,

I'm using the excellent "amavis-logwatch"[1] tool to create a report
about amavisd-new timing statistics. Those are capured with

$log_level = 2;
$syslog_facility = 'local5';
$syslog_priority = 'debug';

and written to a dedicated logilfe as recommended by the documentation
which is provided by amavis-logwatch.

The timing statistics look like this:

,----[ amavisd-new timing statistics ]
| Scan Time Percentiles      % Time   Total (s)        0%        5%       25%   
    50%       75%       95%      100%
| 
-------------------------------------------------------------------------------------------------------------------
| get-file-type2             34.19%     700.358     0.083     0.146     0.152   
  0.157     0.161     0.182     2.242
| SA check                   19.87%     406.995     0.346     0.503     0.720   
  1.062     2.414     4.327    15.734
| SMTP DATA                   7.06%     144.622     0.001     0.022     0.032   
  0.034     0.035     0.036     0.119
| sql-enter                   6.92%     141.678     0.003     0.007     0.010   
  0.012     0.018     0.061     8.747
| fwd-end-chkpnt              5.85%     119.855     0.003     0.004     0.006   
  0.009     0.011     0.060     3.578
| mime_decode                 4.53%      92.754     0.006     0.014     0.016   
  0.016     0.017     0.030     1.688
| main_log_entry              3.05%      62.457     0.007     0.013     0.013   
  0.013     0.014     0.016     0.390
| sql-update                  2.98%      61.024     0.002     0.003     0.004   
  0.004     0.015     0.031     2.416
| fwd-connect                 2.91%      59.570     0.004     0.007     0.008   
  0.008     0.008     0.020     1.073
| lookup_sql                  2.18%      44.624     0.002     0.003     0.005   
  0.005     0.005     0.009     2.322
| fwd-mail-pip                1.37%      28.111     0.001     0.002     0.002   
  0.003     0.003     0.021     0.884
| ...
`----

It is not surprising for me that "SA check" consumes a lot of time -
but I am rather puzzled by the amount of CPu cycles "get-file-type2"
consumed. What exactly is done in "get-file-type2"? Is the ration (one
third of all computing time consumed by it) a normal one ("to be
expected") or is this indicating some serious misconfiguration on my
part?

JFTR, this is an amavisd-new 2.5.3 (Debian package). $MYHOME/tmp is a
normal disk filesystem, not some kind of ram-only fs [2]. My file(1)
utility is:

,----[ file -v output ]
| file-4.17
| magic file from /etc/magic:/usr/share/file/magic
`----


Ciao
Stefan

[1] http://www.mikecappella.com/logwatch/
[2] http://www.arschkrebs.de/postfix/amavisd_tmpfs.shtml
-- 
Stefan Förster     http://www.incertum.net/     Public Key: 0xBBE2A9E9
FdI #284: MCSE - May Certified Stupidity Excel (Holger Lubitz)

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to