Ohai,

As mentioned in a previous mail, we have done a lot of work on OpenSMTPD
to make it more friendly to low CPU/memory environments.

While at it we cleaned up a bit the daemon infrastructure and decided to
merge some of the processes. This is quite visible:

`top` output before:

29704 _smtpd     2    0 2124K 3824K sleep/1   kqread    2:33  0.00% smtpd: 
lookup
24134 _smtpd     2    0 2052K 2652K sleep/1   kqread    1:44  0.00% smtpd: 
control
20270 _smtpd     2    0 2720K 4376K sleep/1   kqread    1:27  0.00% smtpd: smtp
15552 _smtpd     2    0 3528K 5664K sleep/0   kqread    1:02  0.00% smtpd: 
transfer
20194 _smtpd     2    0 2824K 3344K sleep/1   kqread    0:46  0.00% smtpd: 
filter
31356 _smtpd     2    0 1572K 2200K sleep/2   kqread    0:28  0.00% smtpd: 
scheduler
19458 _smtpd     2    0 1728K 2288K sleep/1   kqread    0:28  0.00% smtpd: 
delivery
12412 _smtpq     2    0 2560K 3356K sleep/2   kqread    1:22  0.00% smtpd: queue


`top` output now:

 4091 _smtpd     2    0 1420K 1972K sleep/3   kqread    0:00  0.00% smtpd: 
control
24761 _smtpd     2    0 1396K 3052K sleep/3   kqread    0:00  0.00% smtpd: pony 
express
 1952 _smtpd     2    0 1428K 1956K sleep/1   kqread    0:00  0.00% smtpd: 
lookup
21912 _smtpd     2    0 1224K 1784K sleep/2   kqread    0:00  0.00% smtpd: 
scheduler
31961 _smtpq     2    0 1428K 2036K sleep/2   kqread    0:00  0.00% smtpd: queue


This has no functional changes whatsoever, we are running with this code
in a very heavy loaded environment and there's no contention of any sort
due to the merging.

Now, for the sad part:

The change was very invasive and it was impossible to merge back into
our development branch with the filters and latest cleanups.

We have therefore decided to take a few steps back, get to the latest
version without filters that we could merge to and we will start
adding back the filters code on top of this new clean base.

As a result:

1- filters are not part of the snapshot we just published;
2- you will want to build and report any issue with the snapshot;

The code itself is safe, what is maybe broken is the build stuff

Voila !

-- 
Gilles Chehade

https://www.poolp.org                                          @poolpOrg

-- 
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]

Reply via email to