download zip of files only
Wed Jul 23 11:16:40 HKT 2014
From /weblog/java/performance
How linkedin turn the GC - http://engineering.linkedin.com[..]ughput-and-low-latency-java-applications Using generational & concurrent GC collector - http://www.javacodegeeks.com[..]/04/ibm-jvm-tuning-gencon-gc-policy.html Full VM option list : http://blogs.sun.com/roller/resources/watt/jvm-options-list.html, update for Java7 - http://nerds-central.blogspot.com[..]ot.com/2011/07/all-jvm-7-xx-options.html http://stas-blogspot.blogspot.com[..]ost-complete-list-of-xx-options-for.html A simplified list for some frequency use options - http://rdafbn.blogspot.com.au[..]rbage-collector-guidelines-and-tips.html HotSpot JVM garbage collection options cheat sheet - http://aragozin.blogspot.com[..]spot-jvm-garbage-collection-options.html http://www.oracle.com[..]va/javase/tech/vmoptions-jsp-140102.html An example and story about effect of difference VM parameter affecting the performance - http://www.javaspecialists.eu/archive/Issue191.html Clear the code cache automatically with -XX:+UseCodeCacheFlushing - http://blogs.amd.com[..]time-for-long-running-java-applications/ Discussion about -XX:MinHeapFreeRatio parameter - http://www.gossamer-threads.com[..]s.com/lists/lucene/java-user/44286#44286 The other detailed guide for VM parameters tuning - http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf Here is a more simple cookbook - http://java.sun.com/performance/reference/whitepapers/tuning.html A outdated (1.4) , compehensive but still not really too detailed, overview of various GC tuning - http://www.petefreitag.com/articles/gctuning/ Some say following VM parameter is good enough -server -Xmx -XX:+UseParallelGC http://blogs.sun.com[..]/page/binublog?entry=java_tuning_for_xml Some say is useful if you have huge memory -XX:+UseLargePages http://blogs.sun.com[..]dagastine?entry=java_se_tuning_tip_large Some say below parameter keep GC in low pause -XX:MaxGCPauseMillis=5000 Some say below parameter are very optimal -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:NewSize=1200m -XX:SurvivorRatio=16 http://www.theserverside.com[..]d.tss?thread_id=41258&ASRC=EM_NNL_347804 Some say those parameter is good -XX:+UseConcMarkSweepGC -XX:ParallelCMSThreads=1 -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing -XX:CMSIncrementalDutyCycleMin=0 -XX:CMSIncrementalDutyCycle=10 http://blog.mikiobraun.de/2010/08/cassandra-gc-tuning.html Just in case anyone is curious, the flags enabled by -XX:+AggressiveOpts in JDK 1.6.0_25 are: -XX:+EliminateAutoBox -XX:AutoBoxCacheMax=20000 -XX:BiasedLockingStartupDelay=500 -XX:+DoEscapeAnalysis -XX:+OptimizeStringConcat -XX:+OptimizeFill Generate dump with OOME - -XX:+HeapDumpOnOutOfMemoryError GC log sample of -XX:+UseConcMarkSweepGC -XX:PrintFLSStatistics=1 -XX:+PrintGCDetails - https://gist.github.com/1329783 A case study of tuning VM GC parameters - http://plumbr.eu[..]ld-you-trust-the-default-settings-in-jvm Explanation for few performance related VM parameters - http://www.techpaste.com[..]ine-options-jvm-performance-improvement/
(google search)
(amazon search)
Tue Jul 22 18:04:22 HKT 2014
From /weblog/unix
Web base vim as tutorials - http://www.knowvim.com/ http://www.openvim.com/tutorial.html History of VIM - http://arstechnica.com[..]f-productivity-vims-20th-anniversary.ars Guide for editing text object, most already familiar with using 'w' for word editing, this blog discuss more about using 'p' for paragrahy and other related stuff. - http://blog.carbonfive.com[..]7/vim-text-objects-the-definitive-guide/ Seven habits of effective text editing , a lot of nice tip of using vim, like hlsearch , omni-completion http://www.moolenaar.net/habits.pdf http://video.google.com/videoplay?docid=2538831956647446078 vimdiff tips - http://blog.objectmentor.com[..]cles/2008/04/30/vim-as-a-diff-merge-tool http://gcody.blog.ccidnet.com[..]9899-uid-36931-do-showone-type-blog.html How to regex with line number - http://vim.wikia.com/wiki/Insert_line_numbers_2 cheat sheet of jumping around source code - http://www.faqs.org[..]inux-HOWTO/C-editing-with-VIM-HOWTO.html Nice analysis of good programming environment - http://www.benrady.com[..]why-i-switched-from-textmate-to-vim.html Creating macros in vim - http://smartic.us/2010/02/03/creating-macros-in-vim http://www.markhneedham.com/blog/2010/12/27/vim-learnings-so-far/ <- introduction to Command-T and FuzzyFinder Some VIM tips: Essential Vim editor navigation commands Vim search and replace – 12 powerful find and replace examples. How To add bookmarks inside the Vim editor How To record and play inside the Vim editor Correct spelling mistakes automatically inside the Vim Editor Automatic word completion using Ctrl-X Enable thesaurus option in the Vim editor Vim autocommand magic. Add custom header to your files automatically. Convert Vim editor to a beautiful source code browser. Use the Vim editor as a bash IDE, or C/C++ IDE, or Perl IDE. http://www.thegeekstuff.com/2010/04/vim-editor-tutorial/ ctrl+w, ctrl+w , vimdiff switch folder - hack2live.blogspot.com/2009/02/vimdiff-shortcut-keys.html tutorial - http://javarevisited.blogspot.com[..]editor-in-unix-example-tutorial-and.html Compilation plugin - http://www.vim.org/scripts/script.php?script_id=3115#2.9.3 Highlight multiple searches at the same time, each with a different color. - http://www.vim.org/scripts/script.php?script_id=479 http://www.vim.org/scripts/script.php?script_id=2666#2.6.0 C/C++ IDE - http://www.vim.org/scripts/script.php?script_id=213 http://blog.wuwon.id.au[..]10/vim-plugin-for-navigating-c-with.html Suggestion of Hex editors - http://www.lainoox.com/looking-for-a-hex-editor/ Evil, putting vi in emacs - http://spin.atomicobject.com/2013/02/28/emacs-or-vim-evil/ Fixing syntax at solaris, "export TERM=xtermc", ":syntax enable" - http://kdl.nobugware.com/post/2006/12/01/23-xterm-color-on-unix Graph your Vim undo tree in style. - http://sjl.bitbucket.org/gundo.vim/ Introduction to Selecta and Command-T, tool for fuzzy mapping and open files easier - http://marcovaltas.com/2013/12/27/selecta-on-vim-wildignore.html http://superuser.com[..]d-the-vimrc-file-be-located-on-windows-7 Open Visual Studio config as XML - https://groups.google.com/forum/#!topic/vim_use/HzVM9tjJP08
(google search)
(amazon search)
Tue Jul 22 16:46:12 HKT 2014
From /weblog/learning
How to develop imagination - http://blog.sina.com.cn/s/blog_47841af70100ca7r.html 7 Important Creative Thinking Skills - http://www.business-strategy-innovation.com[..]06/7-important-creative-thinking-skills/ Are you interested to be genius? - http://www.studygs.net/genius.htm 4 ways of treating problems Absolution: Ignore the problem and hope it either fixes itself or someone else solves it. Default. Resolution: Either look to the past for previous solutions to the same problem OR identify and remove the causes of the problem. Satisfice. Solution: Analyse using quantitative methods and / or experimentation to try to yield the best possible outcome. Optimise. Dissolution: Eliminate the problem and prevent it from arising again by redesigning the system that has the problem or its containing system. Idealise. http://jchyip.blogspot.hk[..]2012/06/4-ways-of-treating-problems.html 言语的非连贯性, 偏重例子, 一图抵千言，提问，回答。 http://blogs.exmertec.com/elvis/entry/5 http://www.inside.com.tw[..]014/03/05/25-things-ive-learn-about-life 阿师看世界永远像小孩子那样看，对琐碎事物的提问永远本着小孩子的好奇心，提出的问题永远是浅得像一个脑子没有发育得好的人。我是因为答不出他的浅问题而知道做学问要从最简单的层面入手，然后一层一层地加上变化。 一九六九年起我不再读他家之作。这行为八二年回港任教后多受批评，反映着中、西为学之道有别。在此之前的西雅图华大，诺斯、麦基、巴泽尔等人知道我选择不读不仅同意，且往往鼓励。他们知道传统的经济理论有很多问题，认为我是个可以全面革新该传统的人选。我自己当时的想法，是书永远读之无尽，求学有读书的时候，也有思想的时候，思想时可以不读最好不读。 http://blog.sina.com.cn/s/blog_47841af70102uxvx.html 这里有一个原则同学们要记住：不重要的学术作品大可不读，但重要的要反复重读，读多遍。不要相信重要作品的简化阐释，因为作者究竟怎样想我们不可能从简化的阐释中学到。 - http://blog.sina.com.cn/s/blog_47841af70102ux5w.html
(google search)
(amazon search)
Tue Jul 22 15:30:37 HKT 2014
From /weblog/design/distribute
There are two key primary ways of scaling web applications which is in practice today. 1) “Vertical Scalability” - Adding resource within the same logical unit to increase capacity. An example of this would be to add CPUs to an existing server, or expanding storage by adding hard drive on an existing RAID/SAN storage. 2) “Horizontal Scalability” - Adding multiple logical units of resources and making them work as a single unit. Most clustering solutions, distributed file systems, load-balancers help you with horizontal scalability. Scalability can be further sub-classified based on the “scalability factor”. 1) If the scalability factor stays constant as you scale. This is called “linear scalability“. 2) But chances are that some components may not scale as well as others. A scalability factor below 1.0 is called “sub-linear scalability“. 3) Though rare, its possible to get better performance (scalability factor) just by adding more components (i/o across multiple disk spindles in a RAID gets better with more spindles). This is called “supra-linear scalability“. 4) If the application is not designed for scalability, its possible that things can actually get worse as it scales. This is called “negative scalability“. http://www.royans.net/arch/2007/09/22/what-is-scalability/ Report of building web application with 55k pageload with rail - http://shanti.railsblog.com[..]mongrels-handled-a-550k-pageview-digging XMPP a IM protocol about scalability - http://www.process-one.net[..]icle/the_aol_xmpp_scalability_challenge/ Presentation and resources of making you website more scalable - http://www.scribd.com[..]9/Real-World-Web-Performance-Scalability http://www.theserverside.com[..]lications&asrc=EM_NLN_3990118&uid=703565 http://www.theserverside.com[..]ionsPart2&asrc=EM_NLN_3990119&uid=703565 Brian Zimmer, architect at travel startup Yapta, highlights some worst practices jeopardizing the growth and scalability of a system: * The Golden Hammer. Forcing a particular technology to work in ways it was not intended is sometimes counter-productive. Using a database to store key-value pairs is one example. Another example is using threads to program for concurrency. * Resource Abuse. Manage the availability of shared resources because when they fail, by definition, their failure is experienced pervasively rather than in isolation. For example, connection management to the database through a thread pool. * Big Ball of Mud. Failure to manage dependencies inhibits agility and scalability. * Everything or Something. In both code and application dependency management, the worst practice is not understanding the relationships and formulating a model to facilitate their management. Failure to enforce diligent control is a contributing scalability inhibiter. * Forgetting to check the time. To properly scale a system it is imperative to manage the time alloted for requests to be handled. * Hero Pattern. One popular solution to the operation issue is a Hero who can and often will manage the bulk of the operational needs. For a large system of many components this approach does not scale, yet it is one of the most frequently-deployed solutions. * Not automating. A system too dependent on human intervention, frequently the result of having a Hero, is dangerously exposed to issues of reproducibility and hit-by-a-bus syndrome. * Monitoring. Monitoring, like testing, is often one of the first items sacrificed when time is tight. http://highscalability.com/scalability-worst-practices Useful Corporate Blogs that Talk About Scalability - http://highscalability.com[..]l-corporate-blogs-talk-about-scalability Overview of mapreduce and how it compare with other distributed programming model -http://natishalom.typepad.com[..]0/is-mapreduce-going-to-main-stream.html Paper of data store at amazon http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html Discuss how haven't sync can cause performance issue - http://www.theserverside.com[..]lications&asrc=EM_NLN_6273194&uid=703565 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6423457 Discussion about Cloud Based Memory Architectures - http://highscalability.com[..]ased-memory-architectures-next-big-thing http://highscalability.com[..]alability-and-performance-best-practices Interview with google engineer - http://www.zdnet.co.uk[..]gle-at-scale-everything-breaks-40093061/ Surprisingly youtube is blocking - http://highscalability.com[..]e-scalability-lessons-in-30-minutes.html If we are seeing a sustained arrival rate of requests, greater than our system is capable of processing, then something has to give. Having the entire system degrade is not the ideal service we want to give our customers. A better approach would be to process transactions at our systems maximum possible throughput rate, while maintaining a good response time, and rejecting requests above this arrival rate. - http://mechanical-sympathy.blogspot.com.au[..]apply-back-pressure-when-overloaded.html How twitter scaling - http://www.infoq.com/presentations/Twitter-Analytics How Reddit scaling - http://www.infoq.com/presentations/scaling-reddit How infiniteDB prevent locking and IO - http://highscalability.com[..]-scalable-relational-database-manag.html http://highscalability.com[..]ard-way-about-scaling-a-million-use.html http://martin.kleppmann.com[..]2014/03/26/six-things-about-scaling.html The experiences of various big companies, about network issues - http://aphyr.com/posts/288-the-network-is-reliable Stackoverflow, scale without cloud - http://highscalability.com[..]nth-25-servers-and-i.html?SSLoginOk=true
(google search)
(amazon search)
Tue Jul 22 08:57:27 HKT 2014
From /weblog/software_engineering
Examples of stories - http://www.captaindebug.com/2013/06/so-whats-in-story.html Introduction to story point - http://blog.anandvishwanath.in[..]in/2011/03/questioning-story-points.html Imperative vs Declarative Scenarios in User Stories - http://benmabey.com[..]clarative-scenarios-in-user-stories.html Turn good story to great 1. Get your story right 2. The unwritten rule of what goes inside 3. Choose your words carefully 4. Use acronyms sparingly 5. Convention over OVER-complication - http://jcwong.wordpress.com[..]8/08/turning-stories-from-good-to-great/ Checklist for user story - http://marjoriepries.blogspot.com.au[..]hecklist-for-effective-user-stories.html See the picture in your backlog. - http://winnipegagilist.blogspot.ca[..]012/03/how-to-create-user-story-map.html INVEST mnemonic to describe the characteristics of good stories: Independent: the stories can be delivered in any order Negotiable: the details of what's in the story are co-created by the programmers and customer during development. Valuable: the functionality is seen as valuable by the customers or users of the software. Estimable: the programmers can come up with a reasonable estimate for building the story Small: stories should be built in a small amount of time, usually a matter of person-days. Certainly you should be able to build several stories within one iteration. Testable: you should be able to write tests to verify the software for this story works correctly. http://martinfowler.com/bliki/UserStory.html Story Mania, User Incognito, Disastrous Details, Story Handoff, Criteria Crisis - http://www.romanpichler.com[..]er-stories/5-common-user-story-mistakes/ Define Motivations, Don't Define Implementation - http://alanklement.blogspot.de[..]replacing-user-story-with-job-story.html Why large team is not suitable to use user story to collect requirement - http://accelerateddevelopment.blogspot.hk[..]/07/user-stories-dont-work-for-most.html
(google search)
(amazon search)
Sun Jul 20 20:05:36 HKT 2014
From /weblog/software_engineering/team
Building trust for team - http://cocreatr.typepad.com[..]nity-of-practice-and-trust-building.html One nice article about teamwork: Directing (hi directive + lo supportive, for "enthusiastic beginners") Supporting (hi directive + hi supportive, for "disillusioned learners") Coaching (lo directive + hi supportive, for "reluctant contributors") Delegating (lo directive + lo supportive, for "peak performers") http://www.cmcrossroads.com[..]bbthreads/showflat.php?Cat=&Number=64809 Is it a people problem or process problem - http://blog.nayima.be[..]01/21/people-problem-or-process-problem/ importance of teamwork - http://www.butunclebob.com[..]leS.MichaelFeathers.ProgrammingOnYourOwn 5 Dysfunctions of a Team - http://www.anticlue.net/archives/000279.htm A Leaner Start: Reducing Team Setup Times - http://www.infoq.com/articles/pat-kua-onboarding-new , I think article "letting-go" is really insightful - http://www.thekua.com[..]007/09/24/onboarding-strategy-letting-go A good explanation of what is courage, and the result of didn't have courage. It also mention a bit of how to bulit courage within the team, but not much about it - http://www.xprogramming.com/xpmag/NotXP.htm A potential issue of focus too much on people, rely on few heros - http://jchyip.blogspot.com[..]12/people-over-process-misses-point.html Our agile process requires people to spend the effort to listen and talk to each other, working closely. You have to be a people person to like it. It doesn't suit sociopaths. Accidently hiring a sociopath is going to make XP impossible. Trust me, I know. To me this is XP's fundamental weakness. http://jchyip.blogspot.com[..]12/extreme-programmings-fundamental.html What important is team but not idea - http://www.codinghorror.com[..]g/2010/01/cultivate-teams-not-ideas.html http://www.infoq.com/news/2011/11/enable-high-performance-teams http://www.infoq.com/presentations/Co-Making-Great-Products A Measure of Your Team’s Health: How You Treat Your “Idiot” - http://quickbase.intuit.com[..]r-teams-health-how-you-treat-your-idiot/ http://www.inside.com.tw[..]ur-teams-health-how-you-treat-your-idiot
(google search)
(amazon search)
Fri Jul 18 16:36:11 HKT 2014
From /weblog/software_engineering/project
Linus share about project management, most importance is people, and also discuss about tools, how to collabrate people and how to delegate - http://h30565.www3.hp.com[..]Software-Development-Management/ba-p/440 Only the programmer who is going to write the code can schedule it. Any system where management writes a schedule and hands it off to programmers is doomed to fail. Only the programmer who is going to do the work can figure out what steps they will need to take to implement that feature. - http://www.joelonsoftware.com/articles/fog0000000245.html Never, ever let managers tell programmers to reduce an estimate. Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think this kind of motivation is brain-dead. - http://www.joelonsoftware.com/articles/fog0000000245.html Micromanagement or Macromanagement? http://boncey.org/2006_10_29_how_to_mentor_programmers But, unfortunately, as a general rule, Project Managers have no training. Even if they do have training in the form of an MBA, MBA education is impractical and useless; the academic community has completely failed us in this respect. Furthermore, Project Managers are more often based on personal friendships and company politics; they are rarely based on management skill. And, finally, most managers do not acknowledge that management is a skill that they must study and learn so they don't study or learn it. http://discuss.joelonsoftware.com[..]DiscussTopicParent=8469&ixDiscussGroup=5 An explanation of agile, I think it is more about project management - http://blog.objectmentor.com/articles/2007/04/23/short-reach Some common problem of software project management - http://ajaxwidgets.com[..]thomas/9_reasons_why_software_project.bb http://ntschutta.com[..]ou-know-your-project-is-in-trouble-when/ http://www.goodproductmanager.com[..]roduct-management-vs-project-management/ Brief description of thoughtworks codejam - http://blog.nona.name/200804274.html Listen first. Measure later. http://digerati-illuminatus.blogspot.com[..]gspot.com/2008/05/measure-or-listen.html Paper of burn up and burn down - http://alistair.cockburn.us/Earned-value+and+burn+charts Per my understanding, we can say burn down is push by management where DEV work as task consumer and completing per define tasks within limited time; where burn up work in the other way round. Why rewrite usually bad - http://www.jroller.com[..]astianKuebeck/entry/why_version_2_0_will Why need to manage user/client - http://dreamhead.blogbus.com/logs/48408290.html The blog list several software projects fail case study - http://www.codinghorror.com/blog/archives/000588.html The law of late project - http://www.commonsense4commonpeople.net[..]et/2009/11/the-law-of-late-projects.html Friendship, what make one big team working - http://blog.objectmentor.com/articles/2010/04/26/pair-management On an Agile Team, a person is removed from the team by assigning them work. - http://www.agileadvice.com[..]e-between-agile-teams-and-project-teamd/ Some say an method "Impact Mapping" is very useful - http://mysoftwarequality.wordpress.com[..]com/2014/07/15/complexity-is-the-excuse/
(google search)
(amazon search)
|