Re: Question to postscreen and memcache...

2015-11-28 Thread Wietse Venema
Wietse: > What is the latency for looking up information that is NOT in the > memcache? If it is 10 millseconds, then postscreen can handle only > 100 connections per second, and it becomes a performance bottleneck. bi...@dev-ops.pl: > I have no idea what is the latency for lookup not cached infor

Re: Question to postscreen and memcache...

2015-11-28 Thread biuro
W dniu 2015-11-28 03:32, wie...@porcupine.org napisał(a): bi...@dev-ops.pl: W dniu 2015-11-27 16:52, wie...@porcupine.org napisa?(a): > Wietse Venema: >> Django [BOfH]: >> > Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 MX. >> >> LMDB Postfix caches support sharing; non-

Re: Question to postscreen and memcache...

2015-11-27 Thread Wietse Venema
bi...@dev-ops.pl: > W dniu 2015-11-27 16:52, wie...@porcupine.org napisa?(a): > > Wietse Venema: > >> Django [BOfH]: > >> > Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 > >> > MX. > >> > >> LMDB Postfix caches support sharing; non-LMDB caches cannot be > >> shared at all

Re: Question to postscreen and memcache...

2015-11-27 Thread biuro
W dniu 2015-11-27 16:52, wie...@porcupine.org napisał(a): Wietse Venema: Django [BOfH]: > Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 MX. LMDB Postfix caches support sharing; non-LMDB caches cannot be shared at all. To be precise: LMDB Postfix caches support shared

Re: Question to postscreen and memcache...

2015-11-27 Thread Wietse Venema
Wietse Venema: > Django [BOfH]: > > Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 MX. > > LMDB Postfix caches support sharing; non-LMDB caches cannot be > shared at all. To be precise: LMDB Postfix caches support shared access by readers and writers. Other caches cannot b

Re: Question to postscreen and memcache...

2015-11-27 Thread Wietse Venema
Django [BOfH]: > Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 MX. LMDB Postfix caches support sharing; non-LMDB caches cannot be shared at all. However, the Postfix LMDB client requires fcntl locks. If clusterfs does not support fcntl locks, then things will blow up. If

Re: Question to postscreen and memcache...

2015-11-27 Thread Django [BOfH]
HO p@rick! Am 27.11.2015 um 16:20 schrieb Patrick Ben Koetter: > Would it be possible to come up with something that allows to run a cluster of > Postfix hosts, sharing a temporary postscreen whitelist? Ohhh yes. ;) > It would be > desireable to serve a consistent policy throughout all cluster

Re: Question to postscreen and memcache...

2015-11-27 Thread Patrick Ben Koetter
* Wietse Venema : > Django [BOfH]: > > Hi List, > > > > while looking to the Postfix-Doku under: > > > > http://www.postfix.org/POSTSCREEN_README.html#temp_white_sharing > > > > we keep an eye on the Example 4: > > As documented, the whitelist in that example "can be shared only > between posts

Re: Question to postscreen and memcache...

2015-11-27 Thread Django [BOfH]
Hello Wietse, Am 27.11.2015 um 16:08 schrieb Wietse Venema: > As documented, the whitelist in that example "can be shared only > between postscreen(8) daemons that run under the same master(8) > daemon". Hmmm, O.K. we discussed a further way. Via clusterfs Klaus may share /var/lib/postfix/cache

Re: Question to postscreen and memcache...

2015-11-27 Thread Wietse Venema
Django [BOfH]: > Hi List, > > while looking to the Postfix-Doku under: > > http://www.postfix.org/POSTSCREEN_README.html#temp_white_sharing > > we keep an eye on the Example 4: As documented, the whitelist in that example "can be shared only between postscreen(8) daemons that run under the same