zero1infinity + optimization   98

[no title]
Rob Pike's 5 Rules of Programming

Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is.

Rule 2. Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest.

Rule 3. Fancy algorithms are slow when n is small, and n is usually small. Fancy algorithms have big constants. Until you know that n is frequently going to be big, don't get fancy. (Even if n does get big, use Rule 2 first.)

Rule 4. Fancy algorithms are buggier than simple ones, and they're much harder to implement. Use simple algorithms as well as simple data structures.

Rule 5. Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.

Pike's rules 1 and 2 restate Tony Hoare's famous maxim "Premature optimization is the root of all evil." Ken Thompson rephrased Pike's rules 3 and 4 as "When in doubt, use brute force.". Rules 3 and 4 are instances of the design philosophy KISS. Rule 5 was previously stated by Fred Brooks in The Mythical Man-Month. Rule 5 is often shortened to "write stupid code that uses smart objects".
optimization  programming 
april 2015 by zero1infinity
Less Than Dot - Blog - Bing, Google and Yahoo! announce
s for structured data markup on web pages. With, webmasters and developers can le
seo  google  optimization  webdesign 
june 2011 by zero1infinity
CSS Images and Data URIs - ravelrumba
ve even one CSS image that must be served regularly you’re likely to encounter a performance penalty. The degree of the penalty depends on the size of your data URI CSS file, the size of the remaining image(s), and how many ot
css  tips  html  performance  optimization  data  uri 
december 2009 by zero1infinity
MySQL query optimization | Marius Stanciu Sergiu's weblog
g this feature on helps you to track all SQL queries which took longer than you expected. You can define your expectations in seconds using parameter long_query_time.

After the logging is turned on you can analyze the log contents using mysqldumpslow command. Ex. the following
mysql  performance  optimization 
september 2009 by zero1infinity
« earlier      
per page:    204080120160

related tags

algorithm  algorithms  analytics  apache  apple  article  automation  browser  cache  client  code  codeigniter  compact  compress  compression  concurrency  converter  css  css-sprites  data  database  debugging  design  development  digg  dom  extension  facebook  firebug  firefox  free  friendfeed  geek  generator  google  gzip  hardware  hiphop  howto  html  html5  http  iis7  image  information  instagram  ios  ipad  jar  javascript  jpeg  jpg  jquery  js  json  lamp  library  linux  list  mac  maintenance  marketing  math  memcache  memcached  microsoft  minify  mobile  mysql  nginx  nosql  online  opensource  optimization  optimize  osx  page  pdf  performance  photoshop  php  png  programming  real  require  requirejs  scaling  scripting  selectors  seo  session  speed  sprite  sprites  sql  statistics  svg  testing  tip  tips  tool  tools  trick  tuner  uri  validation  web  webapp  webdesign  webdev  website  xcode  zip 

Copy this bookmark: