<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_07_17_1630214</id>
	<title>Build Your Own Render Farm</title>
	<author>ScuttleMonkey</author>
	<datestamp>1247856720000</datestamp>
	<htmltext>Another installment of Tom's Hardware's how-to articles has a look at what it might take to <a href="http://www.tomshardware.com/reviews/render-farm-node,2340.html#xtor=RSS-182">build your own render farm</a>.  The article looks at everything from top-to-bottom roll-your-owns to buying things pre-built and the pricing insanity that goes along with it.  <i>"If you are working as a freelance artist in the above-mentioned media, toying with the idea, or doing so as a hobbyist, then building even a small farm will greatly increase your productivity compared to working on a single workstation. Studios can even use this piece as a reference for building new render farms, as we're going to address scaling, power, and cooling issues.  If you're looking at buying a new machine and are thinking of spending big bucks to get a bleeding-edge system, you might want to step back and consider whether it would be more effective to buy the latest and greatest workstation or to spend less by investing in a few additional systems to be used as dedicated render nodes."</i></htmltext>
<tokenext>Another installment of Tom 's Hardware 's how-to articles has a look at what it might take to build your own render farm .
The article looks at everything from top-to-bottom roll-your-owns to buying things pre-built and the pricing insanity that goes along with it .
" If you are working as a freelance artist in the above-mentioned media , toying with the idea , or doing so as a hobbyist , then building even a small farm will greatly increase your productivity compared to working on a single workstation .
Studios can even use this piece as a reference for building new render farms , as we 're going to address scaling , power , and cooling issues .
If you 're looking at buying a new machine and are thinking of spending big bucks to get a bleeding-edge system , you might want to step back and consider whether it would be more effective to buy the latest and greatest workstation or to spend less by investing in a few additional systems to be used as dedicated render nodes .
"</tokentext>
<sentencetext>Another installment of Tom's Hardware's how-to articles has a look at what it might take to build your own render farm.
The article looks at everything from top-to-bottom roll-your-owns to buying things pre-built and the pricing insanity that goes along with it.
"If you are working as a freelance artist in the above-mentioned media, toying with the idea, or doing so as a hobbyist, then building even a small farm will greatly increase your productivity compared to working on a single workstation.
Studios can even use this piece as a reference for building new render farms, as we're going to address scaling, power, and cooling issues.
If you're looking at buying a new machine and are thinking of spending big bucks to get a bleeding-edge system, you might want to step back and consider whether it would be more effective to buy the latest and greatest workstation or to spend less by investing in a few additional systems to be used as dedicated render nodes.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965</id>
	<title>A classic quote</title>
	<author>Anonymous</author>
	<datestamp>1247863680000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>A total of 10 copies of XP (for 10 nodes) may sound like a big expense, but it actually adds $140 per unit, pushing the cost of these machines to about $485 per unit for a dual-core node or $610 per unit for a quad-core configuration.</p></div><p>I think Tom should have rephrased that to put it into perspective: "Don't worry only 20\% of the node cost is from Windows".  I find it amazing that the most expensive component on the cheaper node is Windows XP and on the beefier node, it's nearly the same price as the CPU.  It's even more baffling that this statement appears on the same page in reference to CPU selection:</p><p><div class="quote"><p>It's really all about how much you want to spend here, because this is the single most expensive component required for each node.</p></div><p>Maybe Tom is a secret Linux fan and is hinting that Windows isn't a component but a tax.  Or maybe he's just really bad at math.</p></div>
	</htmltext>
<tokenext>A total of 10 copies of XP ( for 10 nodes ) may sound like a big expense , but it actually adds $ 140 per unit , pushing the cost of these machines to about $ 485 per unit for a dual-core node or $ 610 per unit for a quad-core configuration.I think Tom should have rephrased that to put it into perspective : " Do n't worry only 20 \ % of the node cost is from Windows " .
I find it amazing that the most expensive component on the cheaper node is Windows XP and on the beefier node , it 's nearly the same price as the CPU .
It 's even more baffling that this statement appears on the same page in reference to CPU selection : It 's really all about how much you want to spend here , because this is the single most expensive component required for each node.Maybe Tom is a secret Linux fan and is hinting that Windows is n't a component but a tax .
Or maybe he 's just really bad at math .</tokentext>
<sentencetext>A total of 10 copies of XP (for 10 nodes) may sound like a big expense, but it actually adds $140 per unit, pushing the cost of these machines to about $485 per unit for a dual-core node or $610 per unit for a quad-core configuration.I think Tom should have rephrased that to put it into perspective: "Don't worry only 20\% of the node cost is from Windows".
I find it amazing that the most expensive component on the cheaper node is Windows XP and on the beefier node, it's nearly the same price as the CPU.
It's even more baffling that this statement appears on the same page in reference to CPU selection:It's really all about how much you want to spend here, because this is the single most expensive component required for each node.Maybe Tom is a secret Linux fan and is hinting that Windows isn't a component but a tax.
Or maybe he's just really bad at math.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736585</id>
	<title>Amazon EC2</title>
	<author>jdvogt</author>
	<datestamp>1247835060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why not create an image with your render software and deploy as many as you need on EC2?  No hardware cost, no setup time, you only pay for the CPU time you use.</htmltext>
<tokenext>Why not create an image with your render software and deploy as many as you need on EC2 ?
No hardware cost , no setup time , you only pay for the CPU time you use .</tokentext>
<sentencetext>Why not create an image with your render software and deploy as many as you need on EC2?
No hardware cost, no setup time, you only pay for the CPU time you use.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738547</id>
	<title>Re:Part Time Render Farms are cool</title>
	<author>Rtfm42</author>
	<datestamp>1247856840000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The software you're thinking of is Pixar's Alfred.</p></htmltext>
<tokenext>The software you 're thinking of is Pixar 's Alfred .</tokentext>
<sentencetext>The software you're thinking of is Pixar's Alfred.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734003</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736289</id>
	<title>Re:Thanks for this</title>
	<author>dr00g911</author>
	<datestamp>1247833260000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The article neatly sums up how to build a render box from about 5 years ago, or for a hobbyist who doesn't really <i>push</i> the hardware.</p><p>In the last few years, with the prevalence of displacement mapping and linear workflow, file sizes and memory usage to get renders at the quality folks expect of CG work have skyrocketed.</p><p>As someone working as a freelance CG/VFX artist, I can tell you a few practical truths:</p><p>1. You may not need <i>XP 64</i> but you need 64-bit if you hope to do high-resolution, or detailed renders in a single pass. An addendum to this is: don't even consider a motherboard that supports less than 8 gigs of ram, and max the thing out. If you are rendering under Windows, you're shooting yourself in the foot if you're stuck on 32-bit, in particular. You will hit a memory wall with a 4gb RAM system very very quickly. Linux 64 is fine. XP 64 (and even my tests with Win7 64 are good). Avoid Vista 64 like the plague.</p><p>2. Depending on your primary rendering usage, a Core i7 may actually be working against you with hyperthreading. Quite a few of the big boys (Renderman, Mental Ray) are still licensed <i>per thread</i>. With hyperthreading enabled on the motherboard, an i7 looks like 8 cores to many rendering apps. Relevant example: A dual quad Xeon Mac pro can only use half of the machine's processing power as a Mental Ray satellite node with Maya, because it's licensed to only use 8 threads total. In addition, a lot of compositing apps -- and LOTS of plug-ins -- are single-threaded (I'm looking at you, random After Effects plug-in, and just about any dynamics plug-in for a 3d app).  The short of it: if you're going to be rendering with something that's actually capable of saturating a multi-threaded CPU, go for it. But do some research and tests first.</p><p>3. You might be able to get away with a crap mainboard video card -- but make sure of it. A few CG apps don't have command-line rendering available, and it'll suck to learn after the fact that the app you're trying to launch on your pile of new 1U servers won't launch because you don't have a decent video card. Linux &amp; Mac OS (even Hackintoshes) are far superior to Windows in this regard -- you'll rarely find an app that refuses to run due to the card. Crap interactivity is fine as long as you can initiate a render.</p><p>4. Standardize your render boxes AND WORKSTATIONS on a single platform (ie Linux 64, Win 64, MacOS X 10.5 intel). Lots of apps require shaders to be recompiled per platform, and small studios generally use share/freeware stuff that might not be available on all platforms -- it's much better to work around this issue when you're creating your assets, versus when you've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews, but the code isn't available for Linux 64 to render within your lifetime.</p></htmltext>
<tokenext>The article neatly sums up how to build a render box from about 5 years ago , or for a hobbyist who does n't really push the hardware.In the last few years , with the prevalence of displacement mapping and linear workflow , file sizes and memory usage to get renders at the quality folks expect of CG work have skyrocketed.As someone working as a freelance CG/VFX artist , I can tell you a few practical truths : 1 .
You may not need XP 64 but you need 64-bit if you hope to do high-resolution , or detailed renders in a single pass .
An addendum to this is : do n't even consider a motherboard that supports less than 8 gigs of ram , and max the thing out .
If you are rendering under Windows , you 're shooting yourself in the foot if you 're stuck on 32-bit , in particular .
You will hit a memory wall with a 4gb RAM system very very quickly .
Linux 64 is fine .
XP 64 ( and even my tests with Win7 64 are good ) .
Avoid Vista 64 like the plague.2 .
Depending on your primary rendering usage , a Core i7 may actually be working against you with hyperthreading .
Quite a few of the big boys ( Renderman , Mental Ray ) are still licensed per thread .
With hyperthreading enabled on the motherboard , an i7 looks like 8 cores to many rendering apps .
Relevant example : A dual quad Xeon Mac pro can only use half of the machine 's processing power as a Mental Ray satellite node with Maya , because it 's licensed to only use 8 threads total .
In addition , a lot of compositing apps -- and LOTS of plug-ins -- are single-threaded ( I 'm looking at you , random After Effects plug-in , and just about any dynamics plug-in for a 3d app ) .
The short of it : if you 're going to be rendering with something that 's actually capable of saturating a multi-threaded CPU , go for it .
But do some research and tests first.3 .
You might be able to get away with a crap mainboard video card -- but make sure of it .
A few CG apps do n't have command-line rendering available , and it 'll suck to learn after the fact that the app you 're trying to launch on your pile of new 1U servers wo n't launch because you do n't have a decent video card .
Linux &amp; Mac OS ( even Hackintoshes ) are far superior to Windows in this regard -- you 'll rarely find an app that refuses to run due to the card .
Crap interactivity is fine as long as you can initiate a render.4 .
Standardize your render boxes AND WORKSTATIONS on a single platform ( ie Linux 64 , Win 64 , MacOS X 10.5 intel ) .
Lots of apps require shaders to be recompiled per platform , and small studios generally use share/freeware stuff that might not be available on all platforms -- it 's much better to work around this issue when you 're creating your assets , versus when you 've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews , but the code is n't available for Linux 64 to render within your lifetime .</tokentext>
<sentencetext>The article neatly sums up how to build a render box from about 5 years ago, or for a hobbyist who doesn't really push the hardware.In the last few years, with the prevalence of displacement mapping and linear workflow, file sizes and memory usage to get renders at the quality folks expect of CG work have skyrocketed.As someone working as a freelance CG/VFX artist, I can tell you a few practical truths:1.
You may not need XP 64 but you need 64-bit if you hope to do high-resolution, or detailed renders in a single pass.
An addendum to this is: don't even consider a motherboard that supports less than 8 gigs of ram, and max the thing out.
If you are rendering under Windows, you're shooting yourself in the foot if you're stuck on 32-bit, in particular.
You will hit a memory wall with a 4gb RAM system very very quickly.
Linux 64 is fine.
XP 64 (and even my tests with Win7 64 are good).
Avoid Vista 64 like the plague.2.
Depending on your primary rendering usage, a Core i7 may actually be working against you with hyperthreading.
Quite a few of the big boys (Renderman, Mental Ray) are still licensed per thread.
With hyperthreading enabled on the motherboard, an i7 looks like 8 cores to many rendering apps.
Relevant example: A dual quad Xeon Mac pro can only use half of the machine's processing power as a Mental Ray satellite node with Maya, because it's licensed to only use 8 threads total.
In addition, a lot of compositing apps -- and LOTS of plug-ins -- are single-threaded (I'm looking at you, random After Effects plug-in, and just about any dynamics plug-in for a 3d app).
The short of it: if you're going to be rendering with something that's actually capable of saturating a multi-threaded CPU, go for it.
But do some research and tests first.3.
You might be able to get away with a crap mainboard video card -- but make sure of it.
A few CG apps don't have command-line rendering available, and it'll suck to learn after the fact that the app you're trying to launch on your pile of new 1U servers won't launch because you don't have a decent video card.
Linux &amp; Mac OS (even Hackintoshes) are far superior to Windows in this regard -- you'll rarely find an app that refuses to run due to the card.
Crap interactivity is fine as long as you can initiate a render.4.
Standardize your render boxes AND WORKSTATIONS on a single platform (ie Linux 64, Win 64, MacOS X 10.5 intel).
Lots of apps require shaders to be recompiled per platform, and small studios generally use share/freeware stuff that might not be available on all platforms -- it's much better to work around this issue when you're creating your assets, versus when you've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews, but the code isn't available for Linux 64 to render within your lifetime.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734003</id>
	<title>Part Time Render Farms are cool</title>
	<author>mdarksbane</author>
	<datestamp>1247863860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I really loved the system they have set up at ACCAD at Ohio State. They had some clustering software running on all of the workstations that could take it over when it wasn't in use. So you had a very nice computer lab and a render farm all rolled into one. And as a user you could set how much you wanted to share while you were working - so if you were just web browsing, the second core could be churning away on someone's render, but if you were using Maya yourself you could have it all to yourself.</p><p>I really wish I remember what the software was, and I'm sure this is a common arrangement at these sorts of facilities, but I remember being impressed at the execution of it.</p></htmltext>
<tokenext>I really loved the system they have set up at ACCAD at Ohio State .
They had some clustering software running on all of the workstations that could take it over when it was n't in use .
So you had a very nice computer lab and a render farm all rolled into one .
And as a user you could set how much you wanted to share while you were working - so if you were just web browsing , the second core could be churning away on someone 's render , but if you were using Maya yourself you could have it all to yourself.I really wish I remember what the software was , and I 'm sure this is a common arrangement at these sorts of facilities , but I remember being impressed at the execution of it .</tokentext>
<sentencetext>I really loved the system they have set up at ACCAD at Ohio State.
They had some clustering software running on all of the workstations that could take it over when it wasn't in use.
So you had a very nice computer lab and a render farm all rolled into one.
And as a user you could set how much you wanted to share while you were working - so if you were just web browsing, the second core could be churning away on someone's render, but if you were using Maya yourself you could have it all to yourself.I really wish I remember what the software was, and I'm sure this is a common arrangement at these sorts of facilities, but I remember being impressed at the execution of it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734293</id>
	<title>Separate machines are the way to go</title>
	<author>Anonymous</author>
	<datestamp>1247821860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I did this two years ago with four cheap Dell Inspirons ($299 each, with free shipping).  They're thin, easy to stack, and consume less power combined than my desktop.  No discrete graphics, smallest possible HDD; all they need is processors (dual-core) and RAM.  I run a stripped-down Ubuntu on them, and use some Python scripts to distribute Blender render jobs to them over the network, assembling the final frames on a file server.</p><p>Separate machines make an enormous difference.  Even though rendering is relatively amenable to parallelization, a quad core machine isn't nearly as fast as two dual-core machines with the same specs.  Even today, you would have to spend an awful lot of money to get a single machine that renders animations as fast as my two-year-old cluster of four.</p><p>I could even have built my own machines, and saved a few tens of dollars per machine, but the price was already pretty reasonable.</p></htmltext>
<tokenext>I did this two years ago with four cheap Dell Inspirons ( $ 299 each , with free shipping ) .
They 're thin , easy to stack , and consume less power combined than my desktop .
No discrete graphics , smallest possible HDD ; all they need is processors ( dual-core ) and RAM .
I run a stripped-down Ubuntu on them , and use some Python scripts to distribute Blender render jobs to them over the network , assembling the final frames on a file server.Separate machines make an enormous difference .
Even though rendering is relatively amenable to parallelization , a quad core machine is n't nearly as fast as two dual-core machines with the same specs .
Even today , you would have to spend an awful lot of money to get a single machine that renders animations as fast as my two-year-old cluster of four.I could even have built my own machines , and saved a few tens of dollars per machine , but the price was already pretty reasonable .</tokentext>
<sentencetext>I did this two years ago with four cheap Dell Inspirons ($299 each, with free shipping).
They're thin, easy to stack, and consume less power combined than my desktop.
No discrete graphics, smallest possible HDD; all they need is processors (dual-core) and RAM.
I run a stripped-down Ubuntu on them, and use some Python scripts to distribute Blender render jobs to them over the network, assembling the final frames on a file server.Separate machines make an enormous difference.
Even though rendering is relatively amenable to parallelization, a quad core machine isn't nearly as fast as two dual-core machines with the same specs.
Even today, you would have to spend an awful lot of money to get a single machine that renders animations as fast as my two-year-old cluster of four.I could even have built my own machines, and saved a few tens of dollars per machine, but the price was already pretty reasonable.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738477</id>
	<title>Re:Thanks for this</title>
	<author>im\_thatoneguy</author>
	<datestamp>1247855400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> An addendum to this is: don't even consider a motherboard that supports less than 8 gigs of ram, and max the thing out.</p></div><p>Yes.</p><p><div class="quote"><p>XP 64 (and even my tests with Win7 64 are good). Avoid Vista 64 like the plague.</p></div><p>... No.  We transitioned our entire studio and renderfarm to Vista 64 without incident.  XPx64 had too many software incompatibilities.</p><p><div class="quote"><p>Depending on your primary rendering usage, a Core i7 may actually be working against you with hyperthreading. Quite a few of the big boys (Renderman, Mental Ray) are still licensed per thread.</p> </div><p>Licenses are by the CPU socket not by the number of cores.  The i7 is worth every penny.</p><p><div class="quote"><p> A few CG apps don't have command-line rendering available, and it'll suck to learn after the fact that the app you're trying to launch on your pile of new 1U servers won't launch because you don't have a decent video card. Linux &amp; Mac OS (even Hackintoshes) are far superior to Windows in this regard</p> </div><p>???  Uhhhh... I can't think of a single 3d app which requires a video card.  Every notable 3d app was written before 3d accelleration was common.  They all have software viewport drivers.   I can't think of a single cg app which requires a video card period.</p><p><div class="quote"><p> Lots of apps require shaders to be recompiled per platform, and small studios generally use share/freeware stuff that might not be available on all platforms -- it's much better to work around this issue when you're creating your assets, versus when you've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews, but the code isn't available for Linux 64 to render within your lifetime.</p></div><p>Very true.  I'd say even take it a step further.  Standardize your hardware too.  Buy the same motherboard.  Buy the same CPU.  Keep everything except for video drivers identical.  This will make managing your farm much easier since you can just format and clone instead of bothering with trouble shooting.  A 1 hour HDD clone is faster and easier for solving problems than debugging in most cases.</p></div>
	</htmltext>
<tokenext>An addendum to this is : do n't even consider a motherboard that supports less than 8 gigs of ram , and max the thing out.Yes.XP 64 ( and even my tests with Win7 64 are good ) .
Avoid Vista 64 like the plague.... No. We transitioned our entire studio and renderfarm to Vista 64 without incident .
XPx64 had too many software incompatibilities.Depending on your primary rendering usage , a Core i7 may actually be working against you with hyperthreading .
Quite a few of the big boys ( Renderman , Mental Ray ) are still licensed per thread .
Licenses are by the CPU socket not by the number of cores .
The i7 is worth every penny .
A few CG apps do n't have command-line rendering available , and it 'll suck to learn after the fact that the app you 're trying to launch on your pile of new 1U servers wo n't launch because you do n't have a decent video card .
Linux &amp; Mac OS ( even Hackintoshes ) are far superior to Windows in this regard ? ? ?
Uhhhh... I ca n't think of a single 3d app which requires a video card .
Every notable 3d app was written before 3d accelleration was common .
They all have software viewport drivers .
I ca n't think of a single cg app which requires a video card period .
Lots of apps require shaders to be recompiled per platform , and small studios generally use share/freeware stuff that might not be available on all platforms -- it 's much better to work around this issue when you 're creating your assets , versus when you 've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews , but the code is n't available for Linux 64 to render within your lifetime.Very true .
I 'd say even take it a step further .
Standardize your hardware too .
Buy the same motherboard .
Buy the same CPU .
Keep everything except for video drivers identical .
This will make managing your farm much easier since you can just format and clone instead of bothering with trouble shooting .
A 1 hour HDD clone is faster and easier for solving problems than debugging in most cases .</tokentext>
<sentencetext> An addendum to this is: don't even consider a motherboard that supports less than 8 gigs of ram, and max the thing out.Yes.XP 64 (and even my tests with Win7 64 are good).
Avoid Vista 64 like the plague.... No.  We transitioned our entire studio and renderfarm to Vista 64 without incident.
XPx64 had too many software incompatibilities.Depending on your primary rendering usage, a Core i7 may actually be working against you with hyperthreading.
Quite a few of the big boys (Renderman, Mental Ray) are still licensed per thread.
Licenses are by the CPU socket not by the number of cores.
The i7 is worth every penny.
A few CG apps don't have command-line rendering available, and it'll suck to learn after the fact that the app you're trying to launch on your pile of new 1U servers won't launch because you don't have a decent video card.
Linux &amp; Mac OS (even Hackintoshes) are far superior to Windows in this regard ???
Uhhhh... I can't think of a single 3d app which requires a video card.
Every notable 3d app was written before 3d accelleration was common.
They all have software viewport drivers.
I can't think of a single cg app which requires a video card period.
Lots of apps require shaders to be recompiled per platform, and small studios generally use share/freeware stuff that might not be available on all platforms -- it's much better to work around this issue when you're creating your assets, versus when you've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews, but the code isn't available for Linux 64 to render within your lifetime.Very true.
I'd say even take it a step further.
Standardize your hardware too.
Buy the same motherboard.
Buy the same CPU.
Keep everything except for video drivers identical.
This will make managing your farm much easier since you can just format and clone instead of bothering with trouble shooting.
A 1 hour HDD clone is faster and easier for solving problems than debugging in most cases.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736289</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735061</id>
	<title>Re:Unlatest</title>
	<author>omeomi</author>
	<datestamp>1247825220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p><div class="quote"><p>... or to spend less by investing in a few additional systems to be used as dedicated render nodes.</p></div><p>Especially if you buy used systems. Computer hardware depreciates <i>fast</i>.</p></div><p>Wouldn't it be possible to use Amazon EC2 to set up a scalable render farm?</p></div>
	</htmltext>
<tokenext>... or to spend less by investing in a few additional systems to be used as dedicated render nodes.Especially if you buy used systems .
Computer hardware depreciates fast.Would n't it be possible to use Amazon EC2 to set up a scalable render farm ?</tokentext>
<sentencetext>... or to spend less by investing in a few additional systems to be used as dedicated render nodes.Especially if you buy used systems.
Computer hardware depreciates fast.Wouldn't it be possible to use Amazon EC2 to set up a scalable render farm?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733815</id>
	<title>fp TFuCKER</title>
	<author>Anonymous</author>
	<datestamp>1247862960000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext>would mar BSD's a[t0xedo.org],</htmltext>
<tokenext>would mar BSD 's a [ t0xedo.org ] ,</tokentext>
<sentencetext>would mar BSD's a[t0xedo.org],</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733547</id>
	<title>EIE I/O</title>
	<author>Anonymous</author>
	<datestamp>1247861700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>If you run your render farm on PowerPC's you can put their <a href="http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.aixassem/doc/alangref/eieio.htm" title="ibm.com" rel="nofollow">eieio instruction</a> [ibm.com] to good use!!!!!</p></htmltext>
<tokenext>If you run your render farm on PowerPC 's you can put their eieio instruction [ ibm.com ] to good use ! ! ! !
!</tokentext>
<sentencetext>If you run your render farm on PowerPC's you can put their eieio instruction [ibm.com] to good use!!!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734255</id>
	<title>Re:How to Jump Your Own Shark!</title>
	<author>Hurricane78</author>
	<datestamp>1247821740000</datestamp>
	<modclass>None</modclass>
	<modscore>2</modscore>
	<htmltext><p>By the way: Does anyone know a replacement? Something with complete comparison charts on graphics cards, CPUs, etc. Something serious that is not bought by the hardware companies.</p></htmltext>
<tokenext>By the way : Does anyone know a replacement ?
Something with complete comparison charts on graphics cards , CPUs , etc .
Something serious that is not bought by the hardware companies .</tokentext>
<sentencetext>By the way: Does anyone know a replacement?
Something with complete comparison charts on graphics cards, CPUs, etc.
Something serious that is not bought by the hardware companies.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</id>
	<title>4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>BitZtream</author>
	<datestamp>1247863920000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><blockquote><div><p>For memory, 4 GB is a good start. With the availability of inexpensive 4 GB kits (reviewed here), there's no reason not to. If you are using a dual-core processor and your renderer is a 32-bit application, then 4 GB means you'd have just short of the maximum RAM for each core (which is a good idea if your renderer doesn't multi-thread properly).</p></div></blockquote><p>This is where I got off.  I wasn't aware that dual core processors treated ram separately.  Thats news to me, and the guys at AMD, Intel, MS, and Linus as well.  Every OS I'm aware of bases the memory available on the app, not the core, with most 32 bit OSes allowing for about 3G of memory usable to the app (roughly a gig is part of the kernel space for various things in most cases), and allowing for more with some kernel tuning depending on the OS.  I think Linux allows for that, I know Windows and FreeBSD do.</p><p>I also guess he's never heard of PAE?  Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing, meaning a process is more than capable of addressing vastly larger amounts of RAM if its designed to do so, and even without support directly in the application, you can run multiple processes to get the 3G or so per process, which with 2 processes you are at 6.  So if your shitting rendering app is 32 bit, not PAE aware, single threaded and you have more than 1 core than you can just pile on more processes with any modern OS and exceed 4G of usage.  With a real rendering app, i.e. multithreaded, PAE aware and still 32 bit, its a no brainer.  Of course if you're going through the effort to do all this, what are the chances your renderer is going to be 32 bit instead of 64?  This is a question I really do not know as I'm not a render monkey, but I just can't see anything that matters still being a 32 bit app unless RAM really doesn't matter in rendering, which lets face it, for a complex scene, it does.</p><p>Its good to know Tom's has some real techs working for him that understand how computers work.</p></div>
	</htmltext>
<tokenext>For memory , 4 GB is a good start .
With the availability of inexpensive 4 GB kits ( reviewed here ) , there 's no reason not to .
If you are using a dual-core processor and your renderer is a 32-bit application , then 4 GB means you 'd have just short of the maximum RAM for each core ( which is a good idea if your renderer does n't multi-thread properly ) .This is where I got off .
I was n't aware that dual core processors treated ram separately .
Thats news to me , and the guys at AMD , Intel , MS , and Linus as well .
Every OS I 'm aware of bases the memory available on the app , not the core , with most 32 bit OSes allowing for about 3G of memory usable to the app ( roughly a gig is part of the kernel space for various things in most cases ) , and allowing for more with some kernel tuning depending on the OS .
I think Linux allows for that , I know Windows and FreeBSD do.I also guess he 's never heard of PAE ?
Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing , meaning a process is more than capable of addressing vastly larger amounts of RAM if its designed to do so , and even without support directly in the application , you can run multiple processes to get the 3G or so per process , which with 2 processes you are at 6 .
So if your shitting rendering app is 32 bit , not PAE aware , single threaded and you have more than 1 core than you can just pile on more processes with any modern OS and exceed 4G of usage .
With a real rendering app , i.e .
multithreaded , PAE aware and still 32 bit , its a no brainer .
Of course if you 're going through the effort to do all this , what are the chances your renderer is going to be 32 bit instead of 64 ?
This is a question I really do not know as I 'm not a render monkey , but I just ca n't see anything that matters still being a 32 bit app unless RAM really does n't matter in rendering , which lets face it , for a complex scene , it does.Its good to know Tom 's has some real techs working for him that understand how computers work .</tokentext>
<sentencetext>For memory, 4 GB is a good start.
With the availability of inexpensive 4 GB kits (reviewed here), there's no reason not to.
If you are using a dual-core processor and your renderer is a 32-bit application, then 4 GB means you'd have just short of the maximum RAM for each core (which is a good idea if your renderer doesn't multi-thread properly).This is where I got off.
I wasn't aware that dual core processors treated ram separately.
Thats news to me, and the guys at AMD, Intel, MS, and Linus as well.
Every OS I'm aware of bases the memory available on the app, not the core, with most 32 bit OSes allowing for about 3G of memory usable to the app (roughly a gig is part of the kernel space for various things in most cases), and allowing for more with some kernel tuning depending on the OS.
I think Linux allows for that, I know Windows and FreeBSD do.I also guess he's never heard of PAE?
Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing, meaning a process is more than capable of addressing vastly larger amounts of RAM if its designed to do so, and even without support directly in the application, you can run multiple processes to get the 3G or so per process, which with 2 processes you are at 6.
So if your shitting rendering app is 32 bit, not PAE aware, single threaded and you have more than 1 core than you can just pile on more processes with any modern OS and exceed 4G of usage.
With a real rendering app, i.e.
multithreaded, PAE aware and still 32 bit, its a no brainer.
Of course if you're going through the effort to do all this, what are the chances your renderer is going to be 32 bit instead of 64?
This is a question I really do not know as I'm not a render monkey, but I just can't see anything that matters still being a 32 bit app unless RAM really doesn't matter in rendering, which lets face it, for a complex scene, it does.Its good to know Tom's has some real techs working for him that understand how computers work.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735221</id>
	<title>Re:4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>jeffliott</author>
	<datestamp>1247826240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My memory is a little foggy lately, since I've been hanging around in userland a bit, but I'm fairly certain that using long-mode (64-bit) on modern Intel CPU's for your OS and application would yield plenty of virtual address space, using PAE. Additionally, PAE supports a lot more than 36 bits of addressing on the most recent processors, up to 51 I think. The bigger question, is it practical for one CPU to use all that memory?</p></htmltext>
<tokenext>My memory is a little foggy lately , since I 've been hanging around in userland a bit , but I 'm fairly certain that using long-mode ( 64-bit ) on modern Intel CPU 's for your OS and application would yield plenty of virtual address space , using PAE .
Additionally , PAE supports a lot more than 36 bits of addressing on the most recent processors , up to 51 I think .
The bigger question , is it practical for one CPU to use all that memory ?</tokentext>
<sentencetext>My memory is a little foggy lately, since I've been hanging around in userland a bit, but I'm fairly certain that using long-mode (64-bit) on modern Intel CPU's for your OS and application would yield plenty of virtual address space, using PAE.
Additionally, PAE supports a lot more than 36 bits of addressing on the most recent processors, up to 51 I think.
The bigger question, is it practical for one CPU to use all that memory?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733561</id>
	<title>What's Next?</title>
	<author>Anonymous</author>
	<datestamp>1247861760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So when are they gonna make the follow-up about how to start your own organic render farm?</p></htmltext>
<tokenext>So when are they gon na make the follow-up about how to start your own organic render farm ?</tokentext>
<sentencetext>So when are they gonna make the follow-up about how to start your own organic render farm?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734885</id>
	<title>Re:Playstation 2?</title>
	<author>MobileTatsu-NJG</author>
	<datestamp>1247824320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>PS2s are cheap now, and I know they've had linux running on them for some time.  Has anyone managed to get something like ClusterKnoppix running on PS2 hardware?  A renderfarm of slim PS2s sitting on a bookshelf would be kind of neat looking.</p></div><p>The lack of RAM on-board a PS2 (or even a PS3) would make that exercise little more than academic.</p></div>
	</htmltext>
<tokenext>PS2s are cheap now , and I know they 've had linux running on them for some time .
Has anyone managed to get something like ClusterKnoppix running on PS2 hardware ?
A renderfarm of slim PS2s sitting on a bookshelf would be kind of neat looking.The lack of RAM on-board a PS2 ( or even a PS3 ) would make that exercise little more than academic .</tokentext>
<sentencetext>PS2s are cheap now, and I know they've had linux running on them for some time.
Has anyone managed to get something like ClusterKnoppix running on PS2 hardware?
A renderfarm of slim PS2s sitting on a bookshelf would be kind of neat looking.The lack of RAM on-board a PS2 (or even a PS3) would make that exercise little more than academic.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734143</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733891</id>
	<title>Re:Recycling?</title>
	<author>mcgrew</author>
	<datestamp>1247863320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>My grandparents rendered on their small farm, but unfortunately I hate lye soap.</p></htmltext>
<tokenext>My grandparents rendered on their small farm , but unfortunately I hate lye soap .</tokentext>
<sentencetext>My grandparents rendered on their small farm, but unfortunately I hate lye soap.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734805</id>
	<title>Re:4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>Anonymous</author>
	<datestamp>1247823900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>There is still a potential advantage of using a 32-bit renderer when 64-bit is available: 64-bit pointers are twice as big as 32-bit pointers.  That's no big deal for regular memory, but it's a big deal if it causes you to overflow cache.  If your application isn't using the additional address space, in worse-case circumstances a 32-bit application would run with effectively twice the cache space as a 64-bit app.</p></htmltext>
<tokenext>There is still a potential advantage of using a 32-bit renderer when 64-bit is available : 64-bit pointers are twice as big as 32-bit pointers .
That 's no big deal for regular memory , but it 's a big deal if it causes you to overflow cache .
If your application is n't using the additional address space , in worse-case circumstances a 32-bit application would run with effectively twice the cache space as a 64-bit app .</tokentext>
<sentencetext>There is still a potential advantage of using a 32-bit renderer when 64-bit is available: 64-bit pointers are twice as big as 32-bit pointers.
That's no big deal for regular memory, but it's a big deal if it causes you to overflow cache.
If your application isn't using the additional address space, in worse-case circumstances a 32-bit application would run with effectively twice the cache space as a 64-bit app.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733273</id>
	<title>Ask a Slashdot Pimp</title>
	<author>Anonymous</author>
	<datestamp>1247860380000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Welcome Slashdot to premiere of a new weekly thread that I will be running called "Ask a Slashdot Pimp"!  This thread will be my way of helping to answer the questions from you dateless wonders out there on the topic of girls.  Hopefully with my help you will be able to get a date (and possibly get laid by something other than your own hand).  If this becomes successful enough I will be talking to CmdrTaco to make this a weekly article on Slashdot in order to help more people.  So now that our introductions are done, please post your questions (no trolling please).</p></htmltext>
<tokenext>Welcome Slashdot to premiere of a new weekly thread that I will be running called " Ask a Slashdot Pimp " !
This thread will be my way of helping to answer the questions from you dateless wonders out there on the topic of girls .
Hopefully with my help you will be able to get a date ( and possibly get laid by something other than your own hand ) .
If this becomes successful enough I will be talking to CmdrTaco to make this a weekly article on Slashdot in order to help more people .
So now that our introductions are done , please post your questions ( no trolling please ) .</tokentext>
<sentencetext>Welcome Slashdot to premiere of a new weekly thread that I will be running called "Ask a Slashdot Pimp"!
This thread will be my way of helping to answer the questions from you dateless wonders out there on the topic of girls.
Hopefully with my help you will be able to get a date (and possibly get laid by something other than your own hand).
If this becomes successful enough I will be talking to CmdrTaco to make this a weekly article on Slashdot in order to help more people.
So now that our introductions are done, please post your questions (no trolling please).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735171</id>
	<title>Just go hardware!</title>
	<author>Anonymous</author>
	<datestamp>1247825940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>  Why spend the time using an old software approach to rendering when you can utilize your very fast video card.  Check this out.</p><p><a href="http://www.studiogpu.com/" title="studiogpu.com" rel="nofollow">http://www.studiogpu.com/</a> [studiogpu.com]</p></htmltext>
<tokenext>Why spend the time using an old software approach to rendering when you can utilize your very fast video card .
Check this out.http : //www.studiogpu.com/ [ studiogpu.com ]</tokentext>
<sentencetext>  Why spend the time using an old software approach to rendering when you can utilize your very fast video card.
Check this out.http://www.studiogpu.com/ [studiogpu.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733425</id>
	<title>Re:How to Jump Your Own Shark!</title>
	<author>Saint Stephen</author>
	<datestamp>1247861220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I use AdBlock and mostly just look at the Articles section, it's still mostly the same old Tom's we remember.</p><p>I think there just aren't that many articles about cards coming out lately, and they have to do something to fill the time.  I still like it okay (with adblock).</p></htmltext>
<tokenext>I use AdBlock and mostly just look at the Articles section , it 's still mostly the same old Tom 's we remember.I think there just are n't that many articles about cards coming out lately , and they have to do something to fill the time .
I still like it okay ( with adblock ) .</tokentext>
<sentencetext>I use AdBlock and mostly just look at the Articles section, it's still mostly the same old Tom's we remember.I think there just aren't that many articles about cards coming out lately, and they have to do something to fill the time.
I still like it okay (with adblock).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734243</id>
	<title>Re:Recycling?</title>
	<author>Trent Hawkins</author>
	<datestamp>1247821680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Build a massive render farm out thousands of 286's!</p></div><p>except they'll run out of memory and crash on every scene.</p></div>
	</htmltext>
<tokenext>Build a massive render farm out thousands of 286 's ! except they 'll run out of memory and crash on every scene .</tokentext>
<sentencetext>Build a massive render farm out thousands of 286's!except they'll run out of memory and crash on every scene.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735159</id>
	<title>Re:Playstation 2?</title>
	<author>kwark</author>
	<datestamp>1247825880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My guess is that a PS3 is more than 4 times as fast.</p><p>For example I could find a distributed.net benchmark for a PS2 running the rc5-64 challenge at 0.3Mkeys/s. 1 (of the 6 available) SPE from a PS3 will do rc5-72 at 24Mkeys/s. No idea what the difference in GPU performance would be.</p></htmltext>
<tokenext>My guess is that a PS3 is more than 4 times as fast.For example I could find a distributed.net benchmark for a PS2 running the rc5-64 challenge at 0.3Mkeys/s .
1 ( of the 6 available ) SPE from a PS3 will do rc5-72 at 24Mkeys/s .
No idea what the difference in GPU performance would be .</tokentext>
<sentencetext>My guess is that a PS3 is more than 4 times as fast.For example I could find a distributed.net benchmark for a PS2 running the rc5-64 challenge at 0.3Mkeys/s.
1 (of the 6 available) SPE from a PS3 will do rc5-72 at 24Mkeys/s.
No idea what the difference in GPU performance would be.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734143</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28755627</id>
	<title>Re:A classic quote</title>
	<author>Nakarti</author>
	<datestamp>1248101520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>He's really bad at the Greater-Than operand.<br>Have you ever read the graphics reviews?<br>Several times I've read this sequence of ideas:<br>"<br>Card A routinely matches card B, and often blows it away with quality AND framerates...</p><p>For about the same price, card B is definitely a better deal than card A.<br>"<br>Wait........What??</p></htmltext>
<tokenext>He 's really bad at the Greater-Than operand.Have you ever read the graphics reviews ? Several times I 've read this sequence of ideas : " Card A routinely matches card B , and often blows it away with quality AND framerates...For about the same price , card B is definitely a better deal than card A. " Wait........What ?
?</tokentext>
<sentencetext>He's really bad at the Greater-Than operand.Have you ever read the graphics reviews?Several times I've read this sequence of ideas:"Card A routinely matches card B, and often blows it away with quality AND framerates...For about the same price, card B is definitely a better deal than card A."Wait........What?
?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733315</id>
	<title>Unlatest</title>
	<author>fm6</author>
	<datestamp>1247860620000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p><nobr> <wbr></nobr></p><div class="quote"><p>... or to spend less by investing in a few additional systems to be used as dedicated render nodes.</p></div><p>Especially if you buy used systems. Computer hardware depreciates <i>fast</i>.</p></div>
	</htmltext>
<tokenext>... or to spend less by investing in a few additional systems to be used as dedicated render nodes.Especially if you buy used systems .
Computer hardware depreciates fast .</tokentext>
<sentencetext> ... or to spend less by investing in a few additional systems to be used as dedicated render nodes.Especially if you buy used systems.
Computer hardware depreciates fast.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736347</id>
	<title>Helmer?</title>
	<author>dandart</author>
	<datestamp>1247833560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How about Helmer?

<a href="http://helmer.sfe.se/" title="helmer.sfe.se" rel="nofollow">http://helmer.sfe.se/</a> [helmer.sfe.se]</htmltext>
<tokenext>How about Helmer ?
http : //helmer.sfe.se/ [ helmer.sfe.se ]</tokentext>
<sentencetext>How about Helmer?
http://helmer.sfe.se/ [helmer.sfe.se]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736761</id>
	<title>Re:4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>Anonymous</author>
	<datestamp>1247836320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You're the one that may need 'real techs' to help you.</p><p>The way you'd run a 32-bit MentalRay or RenderMan on that render farm optimally on that 64-bit OS is to launch one process per CPU and allocate each process 2 gig.</p><p>This maximizes the render node  because<br>1) neither multithread well; two core isn't going to half the render time.  It's best to render two different frames in single threads instead<br>2) they will use all the memory they are given, 2 gig, but no more (we don't want swapping or fighting over RAM).  So that ends up being 2 gig each processor, as the article says<br>3) if you were to put, say, 8 gig, the top 2 would be useless for the dual code 32-bit renderer.  Therefore, 4 gig is the optimal, price-wize. There is no 6 gig option.</p><p>&gt;I also guess he's never heard of PAE?</p><p>Listen nerds: No one cares about PAE.  No renderer, 3d, video or audio, is implementing it. It's not appropriate for high performance renderer.  No one gives a damn that MySQL can use it, this is an article about render farms, not database servers.</p></htmltext>
<tokenext>You 're the one that may need 'real techs ' to help you.The way you 'd run a 32-bit MentalRay or RenderMan on that render farm optimally on that 64-bit OS is to launch one process per CPU and allocate each process 2 gig.This maximizes the render node because1 ) neither multithread well ; two core is n't going to half the render time .
It 's best to render two different frames in single threads instead2 ) they will use all the memory they are given , 2 gig , but no more ( we do n't want swapping or fighting over RAM ) .
So that ends up being 2 gig each processor , as the article says3 ) if you were to put , say , 8 gig , the top 2 would be useless for the dual code 32-bit renderer .
Therefore , 4 gig is the optimal , price-wize .
There is no 6 gig option. &gt; I also guess he 's never heard of PAE ? Listen nerds : No one cares about PAE .
No renderer , 3d , video or audio , is implementing it .
It 's not appropriate for high performance renderer .
No one gives a damn that MySQL can use it , this is an article about render farms , not database servers .</tokentext>
<sentencetext>You're the one that may need 'real techs' to help you.The way you'd run a 32-bit MentalRay or RenderMan on that render farm optimally on that 64-bit OS is to launch one process per CPU and allocate each process 2 gig.This maximizes the render node  because1) neither multithread well; two core isn't going to half the render time.
It's best to render two different frames in single threads instead2) they will use all the memory they are given, 2 gig, but no more (we don't want swapping or fighting over RAM).
So that ends up being 2 gig each processor, as the article says3) if you were to put, say, 8 gig, the top 2 would be useless for the dual code 32-bit renderer.
Therefore, 4 gig is the optimal, price-wize.
There is no 6 gig option.&gt;I also guess he's never heard of PAE?Listen nerds: No one cares about PAE.
No renderer, 3d, video or audio, is implementing it.
It's not appropriate for high performance renderer.
No one gives a damn that MySQL can use it, this is an article about render farms, not database servers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733785</id>
	<title>Re:Ask a Slashdot Pimp</title>
	<author>Red Flayer</author>
	<datestamp>1247862780000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext>Dear Slashdot Pimp,<br> <br>I am a little confused as to your business plan.  Why would you offer advice to slashdotters on getting laid on their own, when it would be far more profitable to ensure they need to visit your stable of hos to get laid?<br> <br>Might I suggest you acquire the services of a business plan consultant to help you maximize your profits by leveraging the synergisms of your diverse talent pool?  Careful attention to branding (perhaps literally) and marketing could help you achieve your quarterly and yearly targets for growth and margins.<br> <br>Sincerely,<br> <br>Slashdot Business Plan Consultant</htmltext>
<tokenext>Dear Slashdot Pimp , I am a little confused as to your business plan .
Why would you offer advice to slashdotters on getting laid on their own , when it would be far more profitable to ensure they need to visit your stable of hos to get laid ?
Might I suggest you acquire the services of a business plan consultant to help you maximize your profits by leveraging the synergisms of your diverse talent pool ?
Careful attention to branding ( perhaps literally ) and marketing could help you achieve your quarterly and yearly targets for growth and margins .
Sincerely , Slashdot Business Plan Consultant</tokentext>
<sentencetext>Dear Slashdot Pimp, I am a little confused as to your business plan.
Why would you offer advice to slashdotters on getting laid on their own, when it would be far more profitable to ensure they need to visit your stable of hos to get laid?
Might I suggest you acquire the services of a business plan consultant to help you maximize your profits by leveraging the synergisms of your diverse talent pool?
Careful attention to branding (perhaps literally) and marketing could help you achieve your quarterly and yearly targets for growth and margins.
Sincerely, Slashdot Business Plan Consultant</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733273</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733539</id>
	<title>Re:roll-your-own</title>
	<author>Em Emalb</author>
	<datestamp>1247861700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>I tried smoking all that junk that fell in my keyboard but it just smelt like burnt hair.</i></p><p>Dude, if my co-workers' keyboards are any indication of the "typical" keyboard out there, you're damned lucky you didn't kill yourself.</p></htmltext>
<tokenext>I tried smoking all that junk that fell in my keyboard but it just smelt like burnt hair.Dude , if my co-workers ' keyboards are any indication of the " typical " keyboard out there , you 're damned lucky you did n't kill yourself .</tokentext>
<sentencetext>I tried smoking all that junk that fell in my keyboard but it just smelt like burnt hair.Dude, if my co-workers' keyboards are any indication of the "typical" keyboard out there, you're damned lucky you didn't kill yourself.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733389</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267</id>
	<title>How to Jump Your Own Shark!</title>
	<author>Anonymous</author>
	<datestamp>1247860380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>


Considering this article and the <a href="http://hardware.slashdot.org/story/09/07/13/1734220/Building-a-10-TB-Array-For-Around-1000" title="slashdot.org" rel="nofollow">last one from Tom's Hardware</a> [slashdot.org], I cannot wait for the next Tom's Hardware articles:<p><div class="quote"><p>Build Your Own Annoyingly Segmented 10 Page Article!</p></div><p><div class="quote"><p>How to Run Out of Practical DIY Ideas!</p></div><p><div class="quote"><p>Host Your Own Ads for Under $1000!</p></div><p><div class="quote"><p>Turn 50\% of Your Site into Flash Ads in One Day!</p></div><p><div class="quote"><p>How to Fake Content!</p></div><p><div class="quote"><p>Embedding Popup Ads the Automated Way!</p></div><p><div class="quote"><p>Going from Pioneer to Slowly Losing Relevance in 10 Easy Steps!</p></div><p><div class="quote"><p>Earn Pennies a Day By Inconveniencing Your users!</p></div><p> <a href="http://en.wikipedia.org/wiki/Tom's\_Hardware#History" title="wikipedia.org" rel="nofollow">R.I.P. Tom's Hardware</a> [wikipedia.org].</p></div>
	</htmltext>
<tokenext>Considering this article and the last one from Tom 's Hardware [ slashdot.org ] , I can not wait for the next Tom 's Hardware articles : Build Your Own Annoyingly Segmented 10 Page Article ! How to Run Out of Practical DIY Ideas ! Host Your Own Ads for Under $ 1000 ! Turn 50 \ % of Your Site into Flash Ads in One Day ! How to Fake Content ! Embedding Popup Ads the Automated Way ! Going from Pioneer to Slowly Losing Relevance in 10 Easy Steps ! Earn Pennies a Day By Inconveniencing Your users !
R.I.P. Tom 's Hardware [ wikipedia.org ] .</tokentext>
<sentencetext>


Considering this article and the last one from Tom's Hardware [slashdot.org], I cannot wait for the next Tom's Hardware articles:Build Your Own Annoyingly Segmented 10 Page Article!How to Run Out of Practical DIY Ideas!Host Your Own Ads for Under $1000!Turn 50\% of Your Site into Flash Ads in One Day!How to Fake Content!Embedding Popup Ads the Automated Way!Going from Pioneer to Slowly Losing Relevance in 10 Easy Steps!Earn Pennies a Day By Inconveniencing Your users!
R.I.P. Tom's Hardware [wikipedia.org].
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733761</id>
	<title>Cloud computing</title>
	<author>Anonymous</author>
	<datestamp>1247862720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>If your time has value, then buying CPU time from Sun, Amazon, or even Microsoft might be cheaper.</p></htmltext>
<tokenext>If your time has value , then buying CPU time from Sun , Amazon , or even Microsoft might be cheaper .</tokentext>
<sentencetext>If your time has value, then buying CPU time from Sun, Amazon, or even Microsoft might be cheaper.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733857</id>
	<title>render nodes</title>
	<author>Tom</author>
	<datestamp>1247863140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Even a single render node dramatically increases productivity for me.</p><p>I'm doing TG2 skybox renders, something that easily takes 12 hours each, and often two, three, four times that. Having a few render nodes (two at the moment) means I can continue working while a few frames are already rendering. That means more of my time is spent productive and less is spent waiting.</p><p>My render nodes aren't even dedicated machines, just other machines I have around that are mostly idle.</p></htmltext>
<tokenext>Even a single render node dramatically increases productivity for me.I 'm doing TG2 skybox renders , something that easily takes 12 hours each , and often two , three , four times that .
Having a few render nodes ( two at the moment ) means I can continue working while a few frames are already rendering .
That means more of my time is spent productive and less is spent waiting.My render nodes are n't even dedicated machines , just other machines I have around that are mostly idle .</tokentext>
<sentencetext>Even a single render node dramatically increases productivity for me.I'm doing TG2 skybox renders, something that easily takes 12 hours each, and often two, three, four times that.
Having a few render nodes (two at the moment) means I can continue working while a few frames are already rendering.
That means more of my time is spent productive and less is spent waiting.My render nodes aren't even dedicated machines, just other machines I have around that are mostly idle.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734079</id>
	<title>Re:Thanks for this</title>
	<author>copponex</author>
	<datestamp>1247864160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>BTW, what's up with Slashdot javascript? I'm going to have to build a freaking<nobr> <wbr></nobr>/. renderfarm pretty soon, and I'll be sending my receipts to CmdrTaco.</p></div><p>All of the old timers know how to use adblock or we have those freebie accounts. We're a dead marketing segment, and this is part of his evil plan to push us out. The WoW add-on was cruel. But javascript...</p><p>The horror. <i>The horror</i>.</p></div>
	</htmltext>
<tokenext>BTW , what 's up with Slashdot javascript ?
I 'm going to have to build a freaking / .
renderfarm pretty soon , and I 'll be sending my receipts to CmdrTaco.All of the old timers know how to use adblock or we have those freebie accounts .
We 're a dead marketing segment , and this is part of his evil plan to push us out .
The WoW add-on was cruel .
But javascript...The horror .
The horror .</tokentext>
<sentencetext>BTW, what's up with Slashdot javascript?
I'm going to have to build a freaking /.
renderfarm pretty soon, and I'll be sending my receipts to CmdrTaco.All of the old timers know how to use adblock or we have those freebie accounts.
We're a dead marketing segment, and this is part of his evil plan to push us out.
The WoW add-on was cruel.
But javascript...The horror.
The horror.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738439</id>
	<title>Re:A classic quote</title>
	<author>im\_thatoneguy</author>
	<datestamp>1247854560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Windows is just the start.  If you really want to use your renderfarm you're going to want some rendermanagement software to keep it all running.</p><p>Cost per node of Deadline (which I highly recommend) is $140 per computer.   Then of course you've already bought a copy of Maya or Max etc.  $3k.   You might want to use an alternate renderer than Mental Ray.  $1k per workstation.   And you're going to want ghost for equivalent to keep all your computers up to date and get them back to work in the event of a crash.</p><p>Also you're going to need a file server.  If you have more than 10 computers that means Windows Server and CAL licenses.   It's going to need to be a pretty beefy machine to feed GBs of data to the render nodes so expect at least $3k. If you lose all your data this will all be for nothing so you'll want to also be sure you invest in some good backup software.  Also probably want to consider archiving all your old work on tape so I would factor in an LTO drive.</p><p>When you factor in the costs of actualing running a render farm the cost of windows is pretty negligible.</p></htmltext>
<tokenext>Windows is just the start .
If you really want to use your renderfarm you 're going to want some rendermanagement software to keep it all running.Cost per node of Deadline ( which I highly recommend ) is $ 140 per computer .
Then of course you 've already bought a copy of Maya or Max etc .
$ 3k. You might want to use an alternate renderer than Mental Ray .
$ 1k per workstation .
And you 're going to want ghost for equivalent to keep all your computers up to date and get them back to work in the event of a crash.Also you 're going to need a file server .
If you have more than 10 computers that means Windows Server and CAL licenses .
It 's going to need to be a pretty beefy machine to feed GBs of data to the render nodes so expect at least $ 3k .
If you lose all your data this will all be for nothing so you 'll want to also be sure you invest in some good backup software .
Also probably want to consider archiving all your old work on tape so I would factor in an LTO drive.When you factor in the costs of actualing running a render farm the cost of windows is pretty negligible .</tokentext>
<sentencetext>Windows is just the start.
If you really want to use your renderfarm you're going to want some rendermanagement software to keep it all running.Cost per node of Deadline (which I highly recommend) is $140 per computer.
Then of course you've already bought a copy of Maya or Max etc.
$3k.   You might want to use an alternate renderer than Mental Ray.
$1k per workstation.
And you're going to want ghost for equivalent to keep all your computers up to date and get them back to work in the event of a crash.Also you're going to need a file server.
If you have more than 10 computers that means Windows Server and CAL licenses.
It's going to need to be a pretty beefy machine to feed GBs of data to the render nodes so expect at least $3k.
If you lose all your data this will all be for nothing so you'll want to also be sure you invest in some good backup software.
Also probably want to consider archiving all your old work on tape so I would factor in an LTO drive.When you factor in the costs of actualing running a render farm the cost of windows is pretty negligible.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734227</id>
	<title>I already have my render farm.</title>
	<author>Hurricane78</author>
	<datestamp>1247821560000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>It's called a botnet.</p><p>TYVM.</p></htmltext>
<tokenext>It 's called a botnet.TYVM .</tokentext>
<sentencetext>It's called a botnet.TYVM.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734385</id>
	<title>Re:A classic quote</title>
	<author>BitZtream</author>
	<datestamp>1247822280000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Windows is certainly overpriced, no argument there.</p><p>I would argue however that the OS is probably the single largest and most important component of the PC.  While its not a piece of hardware, and it is just one of many required components, its the one that matters the most, I think.</p><p>I mean, change your ram manufacture, you probably won't notice.  Mobo, processor, case, power supply, all these things can change a fair amount and in most cases won't provide an immediately noticeable difference.  The software running on them for the most part won't care.</p><p>Change the OS and the world just changed.  All of your other software needs to be changed in most cases, save for FreeBSD emulating Linux or Wine letting you run Windows binaries, which you're probably not going to want if you're trying to render frames as fast as possible.</p><p>Either way, unless your software requires Windows, I can't imagine why you wouldn't use a free OS for your rendering farm.  Its something you shouldn't really directly interact with after it is setup.  Even if you prefer Windows the desktop/workstation (I do personally) I can't imagine why would would waste the money on licenses when you're probably going to get far superior performance out of something like a cut down, bare bones Linux or FreeBSD install.</p><p>Truth be told, the guy writing the article really isn't all that knowledgeable, as you can tell by his take on how much memory you should use and its limitations mentioned in my other post.</p><p><a href="http://hardware.slashdot.org/comments.pl?sid=1306469&amp;cid=28734027" title="slashdot.org">http://hardware.slashdot.org/comments.pl?sid=1306469&amp;cid=28734027</a> [slashdot.org]</p></htmltext>
<tokenext>Windows is certainly overpriced , no argument there.I would argue however that the OS is probably the single largest and most important component of the PC .
While its not a piece of hardware , and it is just one of many required components , its the one that matters the most , I think.I mean , change your ram manufacture , you probably wo n't notice .
Mobo , processor , case , power supply , all these things can change a fair amount and in most cases wo n't provide an immediately noticeable difference .
The software running on them for the most part wo n't care.Change the OS and the world just changed .
All of your other software needs to be changed in most cases , save for FreeBSD emulating Linux or Wine letting you run Windows binaries , which you 're probably not going to want if you 're trying to render frames as fast as possible.Either way , unless your software requires Windows , I ca n't imagine why you would n't use a free OS for your rendering farm .
Its something you should n't really directly interact with after it is setup .
Even if you prefer Windows the desktop/workstation ( I do personally ) I ca n't imagine why would would waste the money on licenses when you 're probably going to get far superior performance out of something like a cut down , bare bones Linux or FreeBSD install.Truth be told , the guy writing the article really is n't all that knowledgeable , as you can tell by his take on how much memory you should use and its limitations mentioned in my other post.http : //hardware.slashdot.org/comments.pl ? sid = 1306469&amp;cid = 28734027 [ slashdot.org ]</tokentext>
<sentencetext>Windows is certainly overpriced, no argument there.I would argue however that the OS is probably the single largest and most important component of the PC.
While its not a piece of hardware, and it is just one of many required components, its the one that matters the most, I think.I mean, change your ram manufacture, you probably won't notice.
Mobo, processor, case, power supply, all these things can change a fair amount and in most cases won't provide an immediately noticeable difference.
The software running on them for the most part won't care.Change the OS and the world just changed.
All of your other software needs to be changed in most cases, save for FreeBSD emulating Linux or Wine letting you run Windows binaries, which you're probably not going to want if you're trying to render frames as fast as possible.Either way, unless your software requires Windows, I can't imagine why you wouldn't use a free OS for your rendering farm.
Its something you shouldn't really directly interact with after it is setup.
Even if you prefer Windows the desktop/workstation (I do personally) I can't imagine why would would waste the money on licenses when you're probably going to get far superior performance out of something like a cut down, bare bones Linux or FreeBSD install.Truth be told, the guy writing the article really isn't all that knowledgeable, as you can tell by his take on how much memory you should use and its limitations mentioned in my other post.http://hardware.slashdot.org/comments.pl?sid=1306469&amp;cid=28734027 [slashdot.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733381</id>
	<title>This is a factory farm!</title>
	<author>Anonymous</author>
	<datestamp>1247860980000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>The only sustainable approach is to allow the geometry to roam freely outside your coordinate system. And shading should be confined to what can be achieved with natural sun light no matter how low the framerate.</p></htmltext>
<tokenext>The only sustainable approach is to allow the geometry to roam freely outside your coordinate system .
And shading should be confined to what can be achieved with natural sun light no matter how low the framerate .</tokentext>
<sentencetext>The only sustainable approach is to allow the geometry to roam freely outside your coordinate system.
And shading should be confined to what can be achieved with natural sun light no matter how low the framerate.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734399</id>
	<title>ROCKS rocks!</title>
	<author>jfp51</author>
	<datestamp>1247822340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Just download the Rocks Cluster distribution and you will have an operational cluster in about an hour. Doesn't get much more efficient than that</htmltext>
<tokenext>Just download the Rocks Cluster distribution and you will have an operational cluster in about an hour .
Does n't get much more efficient than that</tokentext>
<sentencetext>Just download the Rocks Cluster distribution and you will have an operational cluster in about an hour.
Doesn't get much more efficient than that</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738429</id>
	<title>Re:4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>im\_thatoneguy</author>
	<datestamp>1247854200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Every 32 bit renderer I've used hasn't been able to use more than 3GB.  But you're right if you're still trying to use a 32bit renderer with most scenes you're going to just going to run out of memory and crash.</p><p>64bit + 4+ GB of RAM is pretty much mandatory for production rendering.</p><p>What this article really ignores though is software.  Managing a renderfarm means you want to invest in some great render management software like Frantic Film's deadline.</p></htmltext>
<tokenext>Every 32 bit renderer I 've used has n't been able to use more than 3GB .
But you 're right if you 're still trying to use a 32bit renderer with most scenes you 're going to just going to run out of memory and crash.64bit + 4 + GB of RAM is pretty much mandatory for production rendering.What this article really ignores though is software .
Managing a renderfarm means you want to invest in some great render management software like Frantic Film 's deadline .</tokentext>
<sentencetext>Every 32 bit renderer I've used hasn't been able to use more than 3GB.
But you're right if you're still trying to use a 32bit renderer with most scenes you're going to just going to run out of memory and crash.64bit + 4+ GB of RAM is pretty much mandatory for production rendering.What this article really ignores though is software.
Managing a renderfarm means you want to invest in some great render management software like Frantic Film's deadline.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734143</id>
	<title>Playstation 2?</title>
	<author>Uncle Ira</author>
	<datestamp>1247821260000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>PS2s are cheap now, and I know they've had linux running on them for some time.  Has anyone managed to get something like ClusterKnoppix running on PS2 hardware?  A renderfarm of slim PS2s sitting on a bookshelf would be kind of neat looking.</htmltext>
<tokenext>PS2s are cheap now , and I know they 've had linux running on them for some time .
Has anyone managed to get something like ClusterKnoppix running on PS2 hardware ?
A renderfarm of slim PS2s sitting on a bookshelf would be kind of neat looking .</tokentext>
<sentencetext>PS2s are cheap now, and I know they've had linux running on them for some time.
Has anyone managed to get something like ClusterKnoppix running on PS2 hardware?
A renderfarm of slim PS2s sitting on a bookshelf would be kind of neat looking.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736443</id>
	<title>Re:Unlatest</title>
	<author>mr\_exit</author>
	<datestamp>1247834040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>the bandwidth to Amazon would kill you. It's not uncommon for one frame to pull in gigabytes of textures and geometry needed for the render. Rendering CG is very disk, memory and CPU intensive.</p></htmltext>
<tokenext>the bandwidth to Amazon would kill you .
It 's not uncommon for one frame to pull in gigabytes of textures and geometry needed for the render .
Rendering CG is very disk , memory and CPU intensive .</tokentext>
<sentencetext>the bandwidth to Amazon would kill you.
It's not uncommon for one frame to pull in gigabytes of textures and geometry needed for the render.
Rendering CG is very disk, memory and CPU intensive.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735061</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734901</id>
	<title>An alternate cheap renderfarm.</title>
	<author>Anonymous</author>
	<datestamp>1247824440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Sneak around the office, enabling "xgrid" under the sharing preferences on every mac (rooting is easy if you have local access)<br>Render FCP frames and effects like whoa.<br>Posted anonymously duh !</p></htmltext>
<tokenext>Sneak around the office , enabling " xgrid " under the sharing preferences on every mac ( rooting is easy if you have local access ) Render FCP frames and effects like whoa.Posted anonymously duh !</tokentext>
<sentencetext>Sneak around the office, enabling "xgrid" under the sharing preferences on every mac (rooting is easy if you have local access)Render FCP frames and effects like whoa.Posted anonymously duh !</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736835</id>
	<title>Re:Thanks for this</title>
	<author>pixie.pt</author>
	<datestamp>1247836740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You might have the time, but if you pay 300e for Indigo you'll have (for the moment at least) roughly  24x the horsepower you would get for the same 3 nodes, and 95e for each one you add thereafter. If you trade it for actual hardware you'll see that it is actually less expensive to buy Indigo then using an open source Lux, with the present benefit of having a lifetime update (meaning you'll be granted access to all Indigo versions made).</htmltext>
<tokenext>You might have the time , but if you pay 300e for Indigo you 'll have ( for the moment at least ) roughly 24x the horsepower you would get for the same 3 nodes , and 95e for each one you add thereafter .
If you trade it for actual hardware you 'll see that it is actually less expensive to buy Indigo then using an open source Lux , with the present benefit of having a lifetime update ( meaning you 'll be granted access to all Indigo versions made ) .</tokentext>
<sentencetext>You might have the time, but if you pay 300e for Indigo you'll have (for the moment at least) roughly  24x the horsepower you would get for the same 3 nodes, and 95e for each one you add thereafter.
If you trade it for actual hardware you'll see that it is actually less expensive to buy Indigo then using an open source Lux, with the present benefit of having a lifetime update (meaning you'll be granted access to all Indigo versions made).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738179</id>
	<title>DrDgaf</title>
	<author>Theodore</author>
	<datestamp>1247850600000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Didn't read, don't give a fuck.<br>Building your own cluster can be done by any retard.</p><p>I've been looking into building one for myself, mainly for Blender and LuxRender.<br>Now, if there were CUDA/OpenCL versions for the above programs, the Zotac atom/nvidia-ion boards might be nice, expensive, but nice and low powered (or add PCI geforce 9500's, which would also work with my following idea (why the fuck won't they put a PCI-E/16 on these boards?))...<br>I've been looking into mini-itx mobos (off of Newegg, that mainly shows me zotac geforce 7 series),<br>and intel Wolfdale procs that the reviews say overclock to al least around 3.5G...<br>Add 4G of ram (or whatever the board will take), a gigabit switch, set up PXE or a command line only linux distro off of flash,,,<br>DING!!! FRIES ARE DOEN!!!</p><p>Building your own render farm is easy and cheap if you have half a clue as to what you're doing.<br>Oh,,, knowing where your circuit breakers are when setting it up will help too.</p></htmltext>
<tokenext>Did n't read , do n't give a fuck.Building your own cluster can be done by any retard.I 've been looking into building one for myself , mainly for Blender and LuxRender.Now , if there were CUDA/OpenCL versions for the above programs , the Zotac atom/nvidia-ion boards might be nice , expensive , but nice and low powered ( or add PCI geforce 9500 's , which would also work with my following idea ( why the fuck wo n't they put a PCI-E/16 on these boards ?
) ) ...I 've been looking into mini-itx mobos ( off of Newegg , that mainly shows me zotac geforce 7 series ) ,and intel Wolfdale procs that the reviews say overclock to al least around 3.5G...Add 4G of ram ( or whatever the board will take ) , a gigabit switch , set up PXE or a command line only linux distro off of flash,,,DING ! ! !
FRIES ARE DOEN ! !
! Building your own render farm is easy and cheap if you have half a clue as to what you 're doing.Oh,, , knowing where your circuit breakers are when setting it up will help too .</tokentext>
<sentencetext>Didn't read, don't give a fuck.Building your own cluster can be done by any retard.I've been looking into building one for myself, mainly for Blender and LuxRender.Now, if there were CUDA/OpenCL versions for the above programs, the Zotac atom/nvidia-ion boards might be nice, expensive, but nice and low powered (or add PCI geforce 9500's, which would also work with my following idea (why the fuck won't they put a PCI-E/16 on these boards?
))...I've been looking into mini-itx mobos (off of Newegg, that mainly shows me zotac geforce 7 series),and intel Wolfdale procs that the reviews say overclock to al least around 3.5G...Add 4G of ram (or whatever the board will take), a gigabit switch, set up PXE or a command line only linux distro off of flash,,,DING!!!
FRIES ARE DOEN!!
!Building your own render farm is easy and cheap if you have half a clue as to what you're doing.Oh,,, knowing where your circuit breakers are when setting it up will help too.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734847</id>
	<title>Re:A classic quote</title>
	<author>MobileTatsu-NJG</author>
	<datestamp>1247824080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Maybe Tom is a secret Linux fan and is hinting that Windows isn't a component but a tax.  Or maybe he's just really bad at math.</p></div><p>If he really is trying to say that Windows is a tax and not a component on a render farm then he shouldn't be giving advice on how to build them.</p><p>Render nodes are not like a webserver in the sense that your bases are mostly covered with Open Source alternatives.  Many apps are either limited on their platform support or at least components of them are.  Lightwave, for example, has a Linux-based render node, but won't work with some of the plugins that get sent to it because they're Windows-only.  MotionBuilder isn't supported on Linux at all.  After Effects, to the best of my knowledge, won't run on Linux either.  Depending on the software and on your goals with the render farm, which OS you use is a very important reason for functionality reasons. You could save a few $$ by using Linux, but you may possibly pay for that with loss of functionality.</p><p>To use a fashionably inaccurate metaphor:  Comparing OS's for use with rendering is like comparing an XBOX 360 and a Wii, not like comparing a 360 to a PS3 like you're suggesting he's implying.</p></div>
	</htmltext>
<tokenext>Maybe Tom is a secret Linux fan and is hinting that Windows is n't a component but a tax .
Or maybe he 's just really bad at math.If he really is trying to say that Windows is a tax and not a component on a render farm then he should n't be giving advice on how to build them.Render nodes are not like a webserver in the sense that your bases are mostly covered with Open Source alternatives .
Many apps are either limited on their platform support or at least components of them are .
Lightwave , for example , has a Linux-based render node , but wo n't work with some of the plugins that get sent to it because they 're Windows-only .
MotionBuilder is n't supported on Linux at all .
After Effects , to the best of my knowledge , wo n't run on Linux either .
Depending on the software and on your goals with the render farm , which OS you use is a very important reason for functionality reasons .
You could save a few $ $ by using Linux , but you may possibly pay for that with loss of functionality.To use a fashionably inaccurate metaphor : Comparing OS 's for use with rendering is like comparing an XBOX 360 and a Wii , not like comparing a 360 to a PS3 like you 're suggesting he 's implying .</tokentext>
<sentencetext>Maybe Tom is a secret Linux fan and is hinting that Windows isn't a component but a tax.
Or maybe he's just really bad at math.If he really is trying to say that Windows is a tax and not a component on a render farm then he shouldn't be giving advice on how to build them.Render nodes are not like a webserver in the sense that your bases are mostly covered with Open Source alternatives.
Many apps are either limited on their platform support or at least components of them are.
Lightwave, for example, has a Linux-based render node, but won't work with some of the plugins that get sent to it because they're Windows-only.
MotionBuilder isn't supported on Linux at all.
After Effects, to the best of my knowledge, won't run on Linux either.
Depending on the software and on your goals with the render farm, which OS you use is a very important reason for functionality reasons.
You could save a few $$ by using Linux, but you may possibly pay for that with loss of functionality.To use a fashionably inaccurate metaphor:  Comparing OS's for use with rendering is like comparing an XBOX 360 and a Wii, not like comparing a 360 to a PS3 like you're suggesting he's implying.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736415</id>
	<title>Re:4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>josath</author>
	<datestamp>1247833920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing</p></div><p>Unfortunately both Windows XP and Windows Vista do not support 36-bit addressing in their 32-bit flavors. 32-bit XP &amp; Vista are limited to a little less than 4GB of RAM, no matter what. I think there's a 32-bit uber expensive Server 2008 that supports it, but nobody's gonna be buying that for desktop use or even for render farm use.

However Linux supports it fine, I've happily used 8GB of total RAM while running a completely 32-bit kernel/OS/applications.</p></div>
	</htmltext>
<tokenext>Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressingUnfortunately both Windows XP and Windows Vista do not support 36-bit addressing in their 32-bit flavors .
32-bit XP &amp; Vista are limited to a little less than 4GB of RAM , no matter what .
I think there 's a 32-bit uber expensive Server 2008 that supports it , but nobody 's gon na be buying that for desktop use or even for render farm use .
However Linux supports it fine , I 've happily used 8GB of total RAM while running a completely 32-bit kernel/OS/applications .</tokentext>
<sentencetext>Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressingUnfortunately both Windows XP and Windows Vista do not support 36-bit addressing in their 32-bit flavors.
32-bit XP &amp; Vista are limited to a little less than 4GB of RAM, no matter what.
I think there's a 32-bit uber expensive Server 2008 that supports it, but nobody's gonna be buying that for desktop use or even for render farm use.
However Linux supports it fine, I've happily used 8GB of total RAM while running a completely 32-bit kernel/OS/applications.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28737031</id>
	<title>Re:Thanks for this</title>
	<author>Anonymous</author>
	<datestamp>1247838180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>And if you can't figure out Blender for one reason or another, I know of at least one other 3D app where render nodes happen to run on Wine. <a href="http://www.aceanim.com/Carrara/CarraraOnLinux.html" title="aceanim.com" rel="nofollow">Daz3D's Carrara seems to work for this</a> [aceanim.com]. (Ignore the site design and just read the text.) Carrara is on the low end of the budget of the pay-for apps, yet still is generous enough with features and is probably the easiest to use of the bunch. (Do the other apps use drag and drop for staging and quick shader setup, etc?) Even beyond Carrara I figure most other rendering apps may be compatible for this kind of thing too. If your nodes simply push the calculations through the CPU and don't do much graphically, I don't see why this wouldn't work. But also with such a setup, it might be wise to run the master computer on XP or OSX since the main graphic app may still be looking to access the graphics card, etc.</p></htmltext>
<tokenext>And if you ca n't figure out Blender for one reason or another , I know of at least one other 3D app where render nodes happen to run on Wine .
Daz3D 's Carrara seems to work for this [ aceanim.com ] .
( Ignore the site design and just read the text .
) Carrara is on the low end of the budget of the pay-for apps , yet still is generous enough with features and is probably the easiest to use of the bunch .
( Do the other apps use drag and drop for staging and quick shader setup , etc ?
) Even beyond Carrara I figure most other rendering apps may be compatible for this kind of thing too .
If your nodes simply push the calculations through the CPU and do n't do much graphically , I do n't see why this would n't work .
But also with such a setup , it might be wise to run the master computer on XP or OSX since the main graphic app may still be looking to access the graphics card , etc .</tokentext>
<sentencetext>And if you can't figure out Blender for one reason or another, I know of at least one other 3D app where render nodes happen to run on Wine.
Daz3D's Carrara seems to work for this [aceanim.com].
(Ignore the site design and just read the text.
) Carrara is on the low end of the budget of the pay-for apps, yet still is generous enough with features and is probably the easiest to use of the bunch.
(Do the other apps use drag and drop for staging and quick shader setup, etc?
) Even beyond Carrara I figure most other rendering apps may be compatible for this kind of thing too.
If your nodes simply push the calculations through the CPU and don't do much graphically, I don't see why this wouldn't work.
But also with such a setup, it might be wise to run the master computer on XP or OSX since the main graphic app may still be looking to access the graphics card, etc.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733409</id>
	<title>The need is fading</title>
	<author>Anonymous</author>
	<datestamp>1247861160000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>0</modscore>
	<htmltext><p>I would have been interested but I'm headed in this direction.</p><p>http://www.studiogpu.com/</p><p>It's still needs a few features but 90\% of it will be added before the end of the year and it's a new release. They are even planning to support multiple video cards. Radically cheaper than setting up a render farm.</p></htmltext>
<tokenext>I would have been interested but I 'm headed in this direction.http : //www.studiogpu.com/It 's still needs a few features but 90 \ % of it will be added before the end of the year and it 's a new release .
They are even planning to support multiple video cards .
Radically cheaper than setting up a render farm .</tokentext>
<sentencetext>I would have been interested but I'm headed in this direction.http://www.studiogpu.com/It's still needs a few features but 90\% of it will be added before the end of the year and it's a new release.
They are even planning to support multiple video cards.
Radically cheaper than setting up a render farm.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738655</id>
	<title>Re:4 Gig of ram is the max for 2 procs? WTF?</title>
	<author>dbIII</author>
	<datestamp>1247858940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>I also guess he's never heard of PAE?</p></div> </blockquote><p>The problem is in the Microsoft area only the server versions of 32 bit Microsoft systems have heard of PAE.  Of course everything else has had it since not long after the Pentium Pro came out.</p></div>
	</htmltext>
<tokenext>I also guess he 's never heard of PAE ?
The problem is in the Microsoft area only the server versions of 32 bit Microsoft systems have heard of PAE .
Of course everything else has had it since not long after the Pentium Pro came out .</tokentext>
<sentencetext>I also guess he's never heard of PAE?
The problem is in the Microsoft area only the server versions of 32 bit Microsoft systems have heard of PAE.
Of course everything else has had it since not long after the Pentium Pro came out.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28740321</id>
	<title>Re:A classic quote</title>
	<author>shish</author>
	<datestamp>1247928180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>FreeBSD emulating Linux or Wine letting you run Windows binaries, which you're probably not going to want if you're trying to render frames as fast as possible.</p></div><p>Generally when stuff runs under wine at all, it runs faster<nobr> <wbr></nobr>:-P  Though in this case the load is almost entirely CPU-bound, with very little interaction with the OS, so I can't see it making much difference either way.</p></div>
	</htmltext>
<tokenext>FreeBSD emulating Linux or Wine letting you run Windows binaries , which you 're probably not going to want if you 're trying to render frames as fast as possible.Generally when stuff runs under wine at all , it runs faster : -P Though in this case the load is almost entirely CPU-bound , with very little interaction with the OS , so I ca n't see it making much difference either way .</tokentext>
<sentencetext>FreeBSD emulating Linux or Wine letting you run Windows binaries, which you're probably not going to want if you're trying to render frames as fast as possible.Generally when stuff runs under wine at all, it runs faster :-P  Though in this case the load is almost entirely CPU-bound, with very little interaction with the OS, so I can't see it making much difference either way.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734385</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661</id>
	<title>Thanks for this</title>
	<author>Anonymous</author>
	<datestamp>1247862180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>The article touches on general bits of info that might have been time consuming to find. I live in a small town where commercials for clients like the local chamber of commerce are often put together in iMovie, and delivered in a rush. Recently I was approached by a local art director and was asked about moving from 3D stills (which I do occasionally) to 3D animation to be composited into commercial work (probably for bigger clients than the chamber...). I've determined that I can afford about 2-3 minutes of render time per frame before deadlines really start to get pushed out. So rendering infrastructure is very important.<br> <br>My studio is unique in that I work with open source software, Blender, Lux, etc. And my clients dig it because many of them are into sustainability and see my philosophy as being similar to theirs. I've looked at outsourcing the animation projects to commercial renderfarms, but when you start to "Better Know a Linux Network," you move beyond "get it done" and start to take interest in your own little LAN. Next to my video compositing and 3D graphics books I have a big ol' fat Pro Linux System Administration book, and it's handy, and I like it that way.
<br> <br>The article points out that I can save $140 per node by not needing to buy Windows XP Pro 64 bit edition. This is actually great for me since I typically use the money I save on software to buy more hardware.<br> <br>BTW, what's up with Slashdot javascript? I'm going to have to build a freaking<nobr> <wbr></nobr>/. renderfarm pretty soon, and I'll be sending my receipts to CmdrTaco.</htmltext>
<tokenext>The article touches on general bits of info that might have been time consuming to find .
I live in a small town where commercials for clients like the local chamber of commerce are often put together in iMovie , and delivered in a rush .
Recently I was approached by a local art director and was asked about moving from 3D stills ( which I do occasionally ) to 3D animation to be composited into commercial work ( probably for bigger clients than the chamber... ) .
I 've determined that I can afford about 2-3 minutes of render time per frame before deadlines really start to get pushed out .
So rendering infrastructure is very important .
My studio is unique in that I work with open source software , Blender , Lux , etc .
And my clients dig it because many of them are into sustainability and see my philosophy as being similar to theirs .
I 've looked at outsourcing the animation projects to commercial renderfarms , but when you start to " Better Know a Linux Network , " you move beyond " get it done " and start to take interest in your own little LAN .
Next to my video compositing and 3D graphics books I have a big ol ' fat Pro Linux System Administration book , and it 's handy , and I like it that way .
The article points out that I can save $ 140 per node by not needing to buy Windows XP Pro 64 bit edition .
This is actually great for me since I typically use the money I save on software to buy more hardware .
BTW , what 's up with Slashdot javascript ?
I 'm going to have to build a freaking / .
renderfarm pretty soon , and I 'll be sending my receipts to CmdrTaco .</tokentext>
<sentencetext>The article touches on general bits of info that might have been time consuming to find.
I live in a small town where commercials for clients like the local chamber of commerce are often put together in iMovie, and delivered in a rush.
Recently I was approached by a local art director and was asked about moving from 3D stills (which I do occasionally) to 3D animation to be composited into commercial work (probably for bigger clients than the chamber...).
I've determined that I can afford about 2-3 minutes of render time per frame before deadlines really start to get pushed out.
So rendering infrastructure is very important.
My studio is unique in that I work with open source software, Blender, Lux, etc.
And my clients dig it because many of them are into sustainability and see my philosophy as being similar to theirs.
I've looked at outsourcing the animation projects to commercial renderfarms, but when you start to "Better Know a Linux Network," you move beyond "get it done" and start to take interest in your own little LAN.
Next to my video compositing and 3D graphics books I have a big ol' fat Pro Linux System Administration book, and it's handy, and I like it that way.
The article points out that I can save $140 per node by not needing to buy Windows XP Pro 64 bit edition.
This is actually great for me since I typically use the money I save on software to buy more hardware.
BTW, what's up with Slashdot javascript?
I'm going to have to build a freaking /.
renderfarm pretty soon, and I'll be sending my receipts to CmdrTaco.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734445</id>
	<title>Re:Recycling?</title>
	<author>BitZtream</author>
	<datestamp>1247822520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I tried running SLS Linux on a 286 in somewhere between 92-96, doesn't work so well<nobr> <wbr></nobr>:(</p><p>Yes, I was young and ignorant then about why you REALLY DID have to have a 386 or better.  I just figured it would be slower<nobr> <wbr></nobr>:/</p></htmltext>
<tokenext>I tried running SLS Linux on a 286 in somewhere between 92-96 , does n't work so well : ( Yes , I was young and ignorant then about why you REALLY DID have to have a 386 or better .
I just figured it would be slower : /</tokentext>
<sentencetext>I tried running SLS Linux on a 286 in somewhere between 92-96, doesn't work so well :(Yes, I was young and ignorant then about why you REALLY DID have to have a 386 or better.
I just figured it would be slower :/</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735405</id>
	<title>Re:Ask a Slashdot Pimp</title>
	<author>oatworm</author>
	<datestamp>1247827380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>It's a classic open source strategy.  He's letting the nerds have free sex, then charging for support.  I mean, eventually the nerd will want to know where the clitoris is, right?</htmltext>
<tokenext>It 's a classic open source strategy .
He 's letting the nerds have free sex , then charging for support .
I mean , eventually the nerd will want to know where the clitoris is , right ?</tokentext>
<sentencetext>It's a classic open source strategy.
He's letting the nerds have free sex, then charging for support.
I mean, eventually the nerd will want to know where the clitoris is, right?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733785</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343</id>
	<title>Recycling?</title>
	<author>Anonymous</author>
	<datestamp>1247860740000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>OR - if you get a real job, at a real company, they'll give you their unwanted outdated computers for FREE.</p><p>Seriously! Build a massive render farm out thousands of 286's!</p></htmltext>
<tokenext>OR - if you get a real job , at a real company , they 'll give you their unwanted outdated computers for FREE.Seriously !
Build a massive render farm out thousands of 286 's !</tokentext>
<sentencetext>OR - if you get a real job, at a real company, they'll give you their unwanted outdated computers for FREE.Seriously!
Build a massive render farm out thousands of 286's!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733389</id>
	<title>roll-your-own</title>
	<author>Anonymous</author>
	<datestamp>1247861040000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>"everything from top to bottom roll-your-own to buying things pre-built" Is there some way to get high off computers now? I tried smoking all that junk that fell in my keyboard but it just smelt like burnt hair.</htmltext>
<tokenext>" everything from top to bottom roll-your-own to buying things pre-built " Is there some way to get high off computers now ?
I tried smoking all that junk that fell in my keyboard but it just smelt like burnt hair .</tokentext>
<sentencetext>"everything from top to bottom roll-your-own to buying things pre-built" Is there some way to get high off computers now?
I tried smoking all that junk that fell in my keyboard but it just smelt like burnt hair.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733605</id>
	<title>Re:How to Jump Your Own Shark!</title>
	<author>jedidiah</author>
	<datestamp>1247862000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Both the last "bad idea" and this one really doesn't seem that far removed<br>form a lot of MythTV setups me and some of the users have. MythTV supports<br>a nice little cluster/farm setup where work can be shoved out to other<br>machines that are part of Myth. I have 3 frontend boxes, 2 backend boxes<br>and another desktop machine that can all share video processing duties.</p><p>Large disk arrays are not terribly unusual either.</p></htmltext>
<tokenext>Both the last " bad idea " and this one really does n't seem that far removedform a lot of MythTV setups me and some of the users have .
MythTV supportsa nice little cluster/farm setup where work can be shoved out to othermachines that are part of Myth .
I have 3 frontend boxes , 2 backend boxesand another desktop machine that can all share video processing duties.Large disk arrays are not terribly unusual either .</tokentext>
<sentencetext>Both the last "bad idea" and this one really doesn't seem that far removedform a lot of MythTV setups me and some of the users have.
MythTV supportsa nice little cluster/farm setup where work can be shoved out to othermachines that are part of Myth.
I have 3 frontend boxes, 2 backend boxesand another desktop machine that can all share video processing duties.Large disk arrays are not terribly unusual either.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734243
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733605
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735405
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733785
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733273
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738655
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738429
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734079
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735159
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734143
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734885
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734143
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733891
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28740321
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734385
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738547
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734003
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736443
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735061
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733315
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734805
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28737031
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736835
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733539
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733389
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734445
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28755627
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735221
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738477
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736289
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738439
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736415
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736761
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733425
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_17_1630214_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734255
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734003
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738547
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733661
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736835
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28737031
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736289
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738477
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734079
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733409
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733273
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733785
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735405
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733343
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733891
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734243
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734445
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734143
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735159
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734885
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733381
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733761
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733315
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735061
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736443
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733965
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28755627
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734847
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734385
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28740321
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738439
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734027
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738429
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734805
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736415
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28738655
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28736761
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28735221
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734399
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733547
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733267
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734255
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733605
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733425
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28734227
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_17_1630214.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733389
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_17_1630214.28733539
</commentlist>
</conversation>
