{"id":475,"date":"2006-11-14T10:43:35","date_gmt":"2006-11-14T17:43:35","guid":{"rendered":"http:\/\/www.redmonk.com\/cote\/wp\/?p=475"},"modified":"2006-11-14T10:43:35","modified_gmt":"2006-11-14T17:43:35","slug":"becoming-the-performance-people","status":"publish","type":"post","link":"https:\/\/redmonk.com\/cote\/2006\/11\/14\/becoming-the-performance-people\/","title":{"rendered":"Becoming &quot;The Performance People&quot;"},"content":{"rendered":"<p>Now that Sun&#8217;s chosen the GPL license for Java, there are several opportunities on the table for other folks. Now, these chances were open if you wanted to get into a commercial relationship with Sun in the past, but the dynamics of the relationship can now be different. The obvious first one is being one of the first non-Sun commiters. Here&#8217;s another one that some chatter in <a href=\"\/\/irc.freenode.net#redmonk\">#redmonk<\/a> this morning made me think of:<\/p>\n<h2>&#8220;The Performance People&#8221;<\/h2>\n<p>Chip companies like Intel and AMD can more easily send their teams of people to optimize Java for their chips. Now, they&#8217;ve been doing this already under the old terms, but there&#8217;s a broader chance than just optimizing: these companies could dedicate people to simply working on the overall performance for Java and Java-based code.<\/p>\n<p>Aside from being a good citizen, this could be part of a wider branding story along the lines of &#8220;[Intel|AMD] is a <i>performance<\/i> company. From chips to software, we make things run faster and better.&#8221; Of course, these &#8220;performance people&#8221; would work on more than the JDK and JRE, they&#8217;d volunteer to work on all sorts of open source projects.<\/p>\n<p>My first choice would be <a href=\"http:\/\/jakarta.apache.org\/commons\/\">Jakarta Commons<\/a>; not because commons runs slow or anything, but because it&#8217;s everywhere so any &#8220;performance fixes&#8221; on the table would pay off big time. Eclipse is out there as well. The goal is to target the code that&#8217;s  widely used.<\/p>\n<p>The pool of projects needn&#8217;t be limited to Java either: PHP, ruby, rails, python, and friends would be great as well. And there&#8217;s Mono of course. Sure, you could throw in commercial platforms, but that&#8217;s a different line of thought than this open source noodling.<\/p>\n<h2>What They&#8217;d Do<\/h2>\n<p>For any given project, the performance team would get the code and scour over it for optimizations. If they found anything, they&#8217;d offer some changes to the project teams. Once the performance team was satisfied, they&#8217;d give the project a seal like &#8220;Performance Proven by Company XYZ.&#8221; If you saw the seal, you&#8217;d know the performance people had looked it over and given the project a thumbs up. (No warranty expressed or implied, I&#8217;m sure.)<\/p>\n<p>If there was something particular to their proprietary hardware, sure, they might try to slip that in. But, they&#8217;d soon learn that focusing on overall performance would get them more positive brand-reputation than using a narrow, proprietary focus. Besides, if they sent over crap-patchs, the project teams would\/should just reject them.<\/p>\n<p>As an example: folks are always saying how multi-core chips add in a layer of complexity\/opputunities when it comes to multi-threaded, concurrent programming. I&#8217;d suspect that&#8217;d be one of the core-compentencies of this performance team. I&#8217;m sure there&#8217;s all sorts of graphics and networking optimizations that companies could find, fix, and\/or contribute as well.<\/p>\n<h2>More Benefit from Existing Efforts<\/h2>\n<p>Now, I know that there are already people and companies doing things along these lines. There&#8217;s plenty of people all over who work on performance. In fact, this idea could apply to non-commercial teams as well. The opportunity for chip companies is to profit from the positive PR of such efforts.<\/p>\n<p>Why does that matter? Because in chips brand is a key differentiator. Sure, there&#8217;s always an innovation race, but I&#8217;m always suspicious of that being a stable differentiator, it seems more spikey: everyone is 64 bit now and we&#8217;ve got multi-cores out the wazoo. Put another way, you need more than just the technology itself to differentiate. Remember &#8220;Intel Inside&#8221;? And every company is certainly getting brand-juice out of &#8220;being green.&#8221;<\/p>\n<h2>New Revenue Sources<\/h2>\n<p>The brand idea behind the performance team is to make people think of the company as focused on <i>performance<\/i>, the hardware they happen to sell just happens to be part of that&#8230;a big, <i>big<\/i> part. But, if you wanted something performant other than hardware, you might think of going to that company asking to pay for something new. And there&#8217;s a whole new revenue source, if only indirectly by driving chip sales.<\/p>\n<p><b>Disclaimer:<\/b> Sun and Eclipse are clients.<\/p>\n<p><!-- technorati tags start --><\/p>\n<p>Tags: <a href=\"http:\/\/www.technorati.com\/tag\/intel\" rel=\"tag\">intel<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/amd\" rel=\"tag\">amd<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/performance\" rel=\"tag\">performance<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/gpl\" rel=\"tag\">gpl<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/sunw\" rel=\"tag\">sunw<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/eclipse\" rel=\"tag\">eclipse<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/jdk\" rel=\"tag\">jdk<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/jre\" rel=\"tag\">jre<\/a>, <a href=\"http:\/\/www.technorati.com\/tag\/apache\" rel=\"tag\">apache<\/a><\/p>\n<p><!-- technorati tags end --><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Now that Sun&#8217;s chosen the GPL license for Java, there are several opportunities on the table for other folks. Now, these chances were open if you wanted to get into a commercial relationship with Sun in the past, but the dynamics of the relationship can now be different. The obvious first one is being one [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,15,17,19,23],"tags":[],"class_list":["post-475","post","type-post","status-publish","format-standard","hentry","category-ideas","category-java","category-marketing","category-open-source","category-programming"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/475","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/comments?post=475"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/475\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/media?parent=475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/categories?post=475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/tags?post=475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}