| sysctl -w fs.file-max=12000500 | |
| sysctl -w fs.nr_open=20000500 | |
| ulimit -n 4000000 | |
| sysctl -w net.ipv4.tcp_mem='10000000 10000000 10000000' | |
| sysctl -w net.ipv4.tcp_rmem='1024 4096 16384' | |
| sysctl -w net.ipv4.tcp_wmem='1024 4096 16384' | |
| sysctl -w net.core.rmem_max=16384 | |
| sysctl -w net.core.wmem_max=16384 | |
| wget http://packages.erlang-solutions.com/erlang-solutions_1.0_all.deb | |
| sudo dpkg -i erlang-solutions_1.0_all.deb |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
In React's terminology, there are five core types that are important to distinguish:
React Elements
| package proxy | |
| import ( | |
| "io" | |
| "log" | |
| "net" | |
| ) | |
| func Proxy(srvConn, cliConn *net.TCPConn) { | |
| // channels to wait on the close event for each connection |
This gist started with a collection of resources I was maintaining on stream data processing — also known as distributed logs, data pipelines, event sourcing, CQRS, and other names.
Over time the set of resources grew quite large and I received some interest in a more guided, opinionated path for learning about stream data processing. So I added the reading list.
Please send me feedback!
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.