<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Pro OpenSolaris: A personal favorite I recommend to all</title>
	<atom:link href="http://ctovision.com/2009/05/pro-opensolaris-a-personal-favorite-i-recommend-to-all/feed/" rel="self" type="application/rss+xml" />
	<link>http://ctovision.com/2009/05/pro-opensolaris-a-personal-favorite-i-recommend-to-all/</link>
	<description>News, analysis and context on enterprise technology for the CTO</description>
	<lastBuildDate>Thu, 09 Feb 2012 11:01:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: DayTrader</title>
		<link>http://ctovision.com/2009/05/pro-opensolaris-a-personal-favorite-i-recommend-to-all/#comment-357</link>
		<dc:creator>DayTrader</dc:creator>
		<pubDate>Tue, 19 May 2009 11:35:18 +0000</pubDate>
		<guid isPermaLink="false">http://ctovision.com/?p=378#comment-357</guid>
		<description>The way my system is set up here is always to have large caches to minimize any disk access at all levels of the set up. 
  
 
  
I have multiple front end workstation level computers to access the data that I need to work with and a major size video wall to display all the data on. 
  
 
  
In general there are hundreds of servers running Open Solaris set up into a four tier data stage.  Each level has maximum size caches to minimize their own disk drive access. 
  
 
  
Utilizing the snapshot capability in ZFS it is very easy to migrate data on a LRU basis from one tier to the next. 
  
 
  
The most current data is in the front end tier.  When the drives in the pool become 90% full, stuff is moved up to the next tier, verified as transferred and then deleted after verification until the pool is 70% or less full. 
  
 
  
Each tier is larger than the one under it.  Therefore by the theory of working sets the chance of a hit grows exponentially as you move from one tier to the next. 
  
 
  
Two operations go on her in parallel.  The active usage servers take in the feeds and run a massive set of distributed models to look at the data and present what I want for my purposes. 
  
 
  
Then the last tier of data is used with heavy duty mainframe (IBM full loaded Z9 series computers) to back test the models and recommend feedback for adjusting the tuning and weighting parameters in the models to heuristically tune in on the optimal solution for the models I run. </description>
		<content:encoded><![CDATA[<p>The way my system is set up here is always to have large caches to minimize any disk access at all levels of the set up. </p>
<p>I have multiple front end workstation level computers to access the data that I need to work with and a major size video wall to display all the data on. </p>
<p>In general there are hundreds of servers running Open Solaris set up into a four tier data stage.  Each level has maximum size caches to minimize their own disk drive access. </p>
<p>Utilizing the snapshot capability in ZFS it is very easy to migrate data on a LRU basis from one tier to the next. </p>
<p>The most current data is in the front end tier.  When the drives in the pool become 90% full, stuff is moved up to the next tier, verified as transferred and then deleted after verification until the pool is 70% or less full. </p>
<p>Each tier is larger than the one under it.  Therefore by the theory of working sets the chance of a hit grows exponentially as you move from one tier to the next. </p>
<p>Two operations go on her in parallel.  The active usage servers take in the feeds and run a massive set of distributed models to look at the data and present what I want for my purposes. </p>
<p>Then the last tier of data is used with heavy duty mainframe (IBM full loaded Z9 series computers) to back test the models and recommend feedback for adjusting the tuning and weighting parameters in the models to heuristically tune in on the optimal solution for the models I run.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DayTrader</title>
		<link>http://ctovision.com/2009/05/pro-opensolaris-a-personal-favorite-i-recommend-to-all/#comment-356</link>
		<dc:creator>DayTrader</dc:creator>
		<pubDate>Tue, 19 May 2009 11:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://ctovision.com/?p=378#comment-356</guid>
		<description>I can&#039;t say what , but I use Open Solaris for a lot of my projects here and the main reason is because of the ZFS file system. 
  
 
  
When you get into data running in my server farm hitting thousands of TB and getting ready to push into the PB range the flexibility of ZFS and disk pools without having to resort to all sorts of volume managers and such is awesome. 
  
 
  
I also really like the fact that ZFS gets rid of a lot of holes in hardware raid controllers and silent disk errors. 
  
 
  
As it uses copy on write to deal with transactions and the pool size can be as big as you want , you end up with faster access as the numbers of drives grow, since most of your &#039;working set&#039; of data is already under the heads and doesn&#039;t require seeks. 
  
 
  
With good SSD caches or front end ram based cache systems you can literally end up with only a few percent of your queries even going out to the disk farm. </description>
		<content:encoded><![CDATA[<p>I can&#039;t say what , but I use Open Solaris for a lot of my projects here and the main reason is because of the ZFS file system. </p>
<p>When you get into data running in my server farm hitting thousands of TB and getting ready to push into the PB range the flexibility of ZFS and disk pools without having to resort to all sorts of volume managers and such is awesome. </p>
<p>I also really like the fact that ZFS gets rid of a lot of holes in hardware raid controllers and silent disk errors. </p>
<p>As it uses copy on write to deal with transactions and the pool size can be as big as you want , you end up with faster access as the numbers of drives grow, since most of your &#039;working set&#039; of data is already under the heads and doesn&#039;t require seeks. </p>
<p>With good SSD caches or front end ram based cache systems you can literally end up with only a few percent of your queries even going out to the disk farm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by bobgourley</title>
		<link>http://ctovision.com/2009/05/pro-opensolaris-a-personal-favorite-i-recommend-to-all/#comment-355</link>
		<dc:creator>Twitted by bobgourley</dc:creator>
		<pubDate>Sat, 16 May 2009 12:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://ctovision.com/?p=378#comment-355</guid>
		<description>[...] This post was Twitted by bobgourley - Real-url.org [...] </description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by bobgourley &#8211; Real-url.org [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

