search for: tcp_nopush

...2.3.0 as can be read from the release notes of 2.3.0: This is exactly why it was implemented, a few people complained about the overhead with large numbers of listeners, not only because of the TCP overhead but also the fact that it reduces the write syscall overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable benefits wrt icecast? It might prove helpful if available but more info is needed. > As far as I can see this fix has been applied only for the mp3 format. I > guess the problem still remains for other formats, correct me if I am wrong. It applies to all passthrough s...

Hi there, I''ve got a Rails app that''s a little unusual in that it maintains a database representation of a filesystem (for an image gallery). Thus, if the filesystem is essentially ''out of date'' then the controller''s list action will end up invoking a model update (which involves a filesystem scan). I''m using sqlite3 as this app will be

Klaas Jan Wierenga wrote: >>This is exactly why it was implemented, a few people complained about >>the overhead with large numbers of listeners, not only because of the >>TCP overhead but also the fact that it reduces the write syscall >>overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable >>benefits wrt icecast? It might prove helpful if available but more info >>is needed. > > > As Christopher Baus points out in his article > http://www.baus.net/on-tcp_cork it is not so much the overhead of a few > write calls that affects performan...

...ined?(SO_REUSEPORT) + if RUBY_PLATFORM =~ /(?:alpha|mips|parisc|sparc)/ + SO_REUSEPORT = 0x0200 # untested + else + SO_REUSEPORT = 15 # only tested on x86_64 and i686 + end + end when /freebsd/ # do not send out partial frames (FreeBSD) TCP_NOPUSH = 4 unless defined?(TCP_NOPUSH) @@ -142,9 +151,9 @@ module Unicorn File.umask(old_umask) end elsif /\A\[([a-fA-F0-9:]+)\]:(\d+)\z/ =~ address - new_ipv6_server($1, $2.to_i, opt) + new_tcp_server($1, $2.to_i, opt.merge(:ipv6=>true)) elsif /\A(\d+\.\...

> This is exactly why it was implemented, a few people complained about > the overhead with large numbers of listeners, not only because of the > TCP overhead but also the fact that it reduces the write syscall > overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable > benefits wrt icecast? It might prove helpful if available but more info > is needed. As Christopher Baus points out in his article http://www.baus.net/on-tcp_cork it is not so much the overhead of a few write calls that affects performance, but the overhead in sending...

...r from forking too quickly by sleeping + # sleep 1 # end # # after_fork do |server, worker| + # # per-process listener ports for debugging/admin/migrations # addr = "127.0.0.1:#{9293 + worker.nr}" # server.listen(addr, :tries => -1, :delay => 5, :tcp_nopush => true) # @@ -50,10 +67,6 @@ module Unicorn :worker_processes => 1, :after_fork => lambda { |server, worker| server.logger.info("worker=#{worker.nr} spawned pid=#{$$}") - - # per-process listener ports for debugging/admin: - # addr =...

...worker_connections 2048; } http { passenger_root /usr/lib/ruby/gems/1.8/gems/passenger-3.0.7; passenger_ruby /usr/bin/ruby; include mime.types; default_type application/octet-stream; #access_log /opt/nginx/logs/access.log main; sendfile on; #tcp_nopush on; server { listen 80; server_name localhost; root /var/www/dashboard/current/public; passenger_enabled on; passenger_min_instances 1; # listen 443; # ssl on; # ssl_certificate /opt/nginx/conf/server.crt; # ssl_certificate_k...

...#39;' ''$status $body_bytes_sent "$http_referer" '' ''"$http_user_agent" "$http_x_forwarded_for"''; access_log logs/access.log main; sendfile on; #tcp_nopush on; server_tokens off; #keepalive_timeout 0; keepalive_timeout 120; gzip on; gzip_http_version 1.1; gzip_disable "msie6"; gzip_vary on; gzip_min_length 1100; gzip_buffers 64 8k; gzip_comp_level 3;...

...''$status $body_bytes_sent "$http_referer" '' ''"$http_user_agent" "$http_x_forwarded_for"''; access_log logs/access.log main; sendfile on; # These are good default values. tcp_nopush on; tcp_nodelay off; server_tokens off; keepalive_timeout 65; server { listen 192.168.122.17:8140; server_name primaryca; root /etc/puppet/puppetmaster/public; passenger_enabled on; passenger_use_global_queue on; rails_en...

...deally a kext that implements another ABI personality (much like Linux ABI emulation on Windows) in addition to the BSD personality. In fact the FreeBSD linux compat could be used if the FreeBSD portion of XNU is synced up with current, and we’d get bug fixes for long standing issues like the macOS TCP_NOPUSH bug that has long since been fixed in FreeBSD. > >> Ultimately if you are doing this on your own for your own for fun thats great, but if this something you intend to ship to other people please reconsider. It is more than a theoretical concern that it will break. >> >> Louis...

We're abusing icecast in a true narrowcasting setup (personalized stream per mountpoint). The streams itself are created in a piece of proprietory (spelling?, i'm dutch) software, icecast merely relays them. However, the intended endpoint is an embedded device. This device has trouble with tcp/ip packets not matching the max. packet size (MSS or MSS minus header). After eleborate testing,

> On Jun 6, 2017, at 4:08 PM, Michael Clark via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Folks, > > I’m working on a port of musl libc to macos (arch triple is “x86_64-xnu-musl”) to solve some irreconcilable issues I’m having with libSystem.dylib. I don’t want to use glibc for various reasons, mainly because I want to static link. I have static PIE + ASLR working

Hi all, Tried out the mongrel upload progress plugin with Drb and it works great on my OSX development box, but when putting it into production (Ubuntu Dapper), uploads complete but the app isn''t returning any values for upload progress, and uploads are not showing up in the queue when running upload_client.rb. Before anyone asks, yes, I''m running both the mongrel instances and

Hi Folks, I’m working on a port of musl libc to macos (arch triple is “x86_64-xnu-musl”) to solve some irreconcilable issues I’m having with libSystem.dylib. I don’t want to use glibc for various reasons, mainly because I want to static link. I have static PIE + ASLR working which is not actually supported by the Apple toolchain (*1), but I managed to get it to work. I’m sure Apple might say