Pinboard (jm)
https://pinboard.in/u:jm/public/
recent bookmarks from jmS3 2017-02-28 outage post-mortem2017-03-02T17:59:11+00:00
https://aws.amazon.com/message/41926/
jmThe Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected. At 9:37AM PST, an authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers for one of the S3 subsystems that is used by the S3 billing process. Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended. The servers that were inadvertently removed supported two other S3 subsystems. One of these subsystems, the index subsystem, manages the metadata and location information of all S3 objects in the region. This subsystem is necessary to serve all GET, LIST, PUT, and DELETE requests. The second subsystem, the placement subsystem, manages allocation of new storage and requires the index subsystem to be functioning properly to correctly operate. The placement subsystem is used during PUT requests to allocate storage for new objects. Removing a significant portion of the capacity caused each of these systems to require a full restart. While these subsystems were being restarted, S3 was unable to service requests. Other AWS services in the US-EAST-1 Region that rely on S3 for storage, including the S3 console, Amazon Elastic Compute Cloud (EC2) new instance launches, Amazon Elastic Block Store (EBS) volumes (when data was needed from a S3 snapshot), and AWS Lambda were also impacted while the S3 APIs were unavailable.
]]>s3 postmortem aws post-mortem outages cms opshttps://pinboard.in/https://pinboard.in/u:jm/b:7b0e72366abd/Why Static Website Generators Are The Next Big Thing2015-11-04T10:02:44+00:00
http://www.smashingmagazine.com/2015/11/modern-static-website-generators-next-big-thing/
jmweb html history webmake static-sites bake-dont-fry site-generators cmshttps://pinboard.in/https://pinboard.in/u:jm/b:b32a52814912/Cassandra moving to using G1 as the default recommended GC implementation2015-04-29T15:42:34+00:00
https://issues.apache.org/jira/browse/CASSANDRA-7486
jmcassandra tuning ops g1gc cms gc java jvm production performance memoryhttps://pinboard.in/https://pinboard.in/u:jm/b:0b4b3d1abe38/Squarespace2015-04-17T22:00:25+00:00
http://www.squarespace.com/
jmvia:oisin blog cms design hosting web-design web websiteshttps://pinboard.in/https://pinboard.in/u:jm/b:f9e94f3d504e/Optimizing Java CMS garbage collections, its difficulties, and using JTune as a solution | LinkedIn Engineering2015-04-11T20:21:41+00:00
http://engineering.linkedin.com/java/optimizing-java-cms-garbage-collections-its-difficulties-and-using-jtune-solution
jmjava jvm tuning gc cms linkedin performance opshttps://pinboard.in/https://pinboard.in/u:jm/b:717dfe95f072/Impact of large primitive arrays (BLOBS) on JVM Garbage Collection2014-03-19T12:12:51+00:00
http://java-is-the-new-c.blogspot.ie/2013/07/impact-of-large-primitive-arrays-blobs.html
jmcms java jvm performance optimization tuning off-heap-storage memoryhttps://pinboard.in/https://pinboard.in/u:jm/b:026572f118c8/What drives JVM full GC duration2013-10-08T11:15:46+00:00
http://java-is-the-new-c.blogspot.de/2013/07/what-drives-full-gc-duration-its.html
jmFull GC duration depends on the number of objects allocated and the locality of their references. It does not depend that much on actual heap size.
Reference locality has a surprisingly high effect.]]>java jvm data gc tuning performance cms g1https://pinboard.in/https://pinboard.in/u:jm/b:71efc8abad7c/Tuning and benchmarking Java 7's Garbage Collectors: Default, CMS and G12013-07-25T11:27:30+00:00
http://java-is-the-new-c.blogspot.ie/2013/07/tuning-and-benchmarking-java-7s-garbage.html
jmjava gc tuning jvm cms g1 opshttps://pinboard.in/https://pinboard.in/u:jm/b:6ef833ae0fa3/Java Garbage Collection Distilled2013-06-19T10:07:19+00:00
http://www.infoq.com/articles/Java_Garbage_Collection_Distilled
jmSerial, Parallel, Concurrent, CMS, G1, Young Gen, New Gen, Old Gen, Perm Gen, Eden, Tenured, Survivor Spaces, Safepoints, and the hundreds of JVM start-up flags. Does this all baffle you when trying to tune the garbage collector while trying to get the required throughput and latency from your Java application? If it does then don’t worry, you are not alone. Documentation describing garbage collection feels like man pages for an aircraft. Every knob and dial is detailed and explained but nowhere can you find a guide on how to fly. This article will attempt to explain the tradeoffs when choosing and tuning garbage collection algorithms for a particular workload.
]]>gc java garbage-collection coding cms g1 jvm optimizationhttps://pinboard.in/https://pinboard.in/u:jm/b:f59114d2c748/Everything I Ever Learned About JVM Performance Tuning @Twitter2012-12-01T18:51:22+00:00
http://www.slideshare.net/aszegedi/everything-i-ever-learned-about-jvm-performance-tuning-twitter
jmtuning jvm java gc cms presentations slides twitterhttps://pinboard.in/https://pinboard.in/u:jm/b:80c49db84474/flogr2009-11-06T00:31:06+00:00
http://code.google.com/p/flogr/
jmvia:yoz flickr photos web cms php blogging photoblog gallery slideshow flogrhttps://pinboard.in/u:jm/b:a01eab4f599b/