Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
| views: | |
| - icon: 'mdi:home-variant' | |
| cards: | |
| - card: | |
| show_header_toggle: false | |
| type: entities | |
| entities: | |
| - group_config: | |
| secondary_info: last-changed | |
| type: 'custom:fold-entity-row' |
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
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| Deployment steps for this blog post: | |
| http://kearon.blogspot.co.uk/2015/01/installing-service-using-topshelf-with.html |
| (new-object System.Net.WebClient).DownloadFile('http://dl.google.com/chrome/install/375.126/chrome_installer.exe', 'c:/temp/chrome.exe');. c:/temp/chrome.exe /silent /install;rm c:/temp -rec |
| #chat-box.ubuntu.hidden-xs | |
| .closed | |
| .pull-right | |
| = link_to_function content_tag(:i, nil, class: 'glyphicon glyphicon-chevron-up').html_safe, 'chat.show()' | |
| .m-l-small | |
| = link_to_function 'Chat with us', 'chat.show()' | |
| .opened{style: 'display: none'} | |
| .header | |
| .pull-right | |
| = link_to_function content_tag(:i, nil, class: 'glyphicon glyphicon-plus-sign').html_safe, 'chat.maximize()', class: 'maximize', style: 'display: none' |
| /// <reference path="angular.d.ts"/> | |
| class KittenController { | |
| constructor( | |
| private $scope: ng.IScope, | |
| private debounce: IDebounce | |
| ) { | |
| this.watchForSizeChanges(); | |
| } |
| # | |
| # Assumptions | |
| # | |
| # 1. If you have a Octopus release deployed, say 1.0.0.73, there is a git | |
| # tag set for that commit in GitHub that is "v1.0.0.73". | |
| # | |
| # 2. You have TeamCity label each successful build in GitHub with the format | |
| # "v{build number}. Sidenote: it appears that TeamCity only labels the | |
| # default branch, but not feature branches. | |
| # |
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs