search for: 21x

...cot/dovecot.conf # OS: Linux 2.6.26-1-686 i686 Debian lenny/sid log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3s managesieve listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): 21x.xx.xx.xx:110 listen(managesieve): localhost:2000 ssl_listen(default): 21x.xx.xx.xx:993 ssl_listen(imap): 21x.xx.xx.x:993 ssl_listen(pop3): 21x.xx.xx.xx:995 ssl_listen(managesieve): ssl_ca_file: /etc/postfix/ssl/ssl.xxxxxxxxx.de.ca-bundle ssl_cert_file: /etc/postfix/ssl/ssl.xxxxxxxxxx.de.cert ssl_k...

I am machines on IPsec VPN which is a subnet of my bigger LAN ( ie I have machines on the LAN which is not in the VPN ), specifically :- 192.168.132.0/29:0 -> internet ---> 192.168.1.192/27:0 ( local subnet ---> internet--> remote subnet ) # ip route list ... 192.168.1.192/27 via 21x.18x.11x.8x dev ipsec0 192.168.1.0/24 via 192.168.15.146 dev eth0 ... Now, the machines in the local subnet ***INSIDE*** 192.168.132.0/29 when accessing remote subnet 192.168.1.192/27 are routed to the internet using VPN and this is behaving correctly. But machines in the local subnet ***OUTSID...

...erformance. In addition, it tends to produce larger binary and profile data file. Our internal C++ benchmarks shows that FE based instrumentation degrades the performance (compared to non-instrumented version) by 58.3%, and in some extreme cases, the application speed/throughput decreases by 95% (21x runtime slowdown). Running the instrumented binary too slow is not desirable in PGO for the following reasons: * This slows down already lengthy build time. In the worst case, the instrumented binary is so slow that it fails to run a representative workload, because slow execution can leads to...

...tends to produce larger binary and profile data file. Our internal C++ >> benchmarks shows that FE based instrumentation degrades the performance >> (compared to non-instrumented version) by 58.3%, and in some extreme cases, >> the application speed/throughput decreases by 95% (21x runtime slowdown). >> >> Running the instrumented binary too slow is not desirable in PGO for the >> following reasons: >> * This slows down already lengthy build time. In the worst case, the >> instrumented binary is so slow that it fails to run a representative &g...

...profile data file. Our internal > C++ > >>> benchmarks shows that FE based instrumentation degrades the performance > >>> (compared to non-instrumented version) by 58.3%, and in some extreme > cases, > >>> the application speed/throughput decreases by 95% (21x runtime > slowdown). > >>> > >>> Running the instrumented binary too slow is not desirable in PGO for > the > >>> following reasons: > >>> * This slows down already lengthy build time. In the worst case, the > >>> instrumented bin...