<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/vizstack/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/vizstack/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 23 Feb 2011 01:34:30 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/vizstack/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>viz-paraview making use of more CPU cores per GPU</title><link>https://sourceforge.net/p/vizstack/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The Paraview people recommend making use of multiple available CPU cores per GPU ( see &lt;a href="http://www.vtk.org/Wiki/Setting_up_a_ParaView_Server\" rel="nofollow"&gt;http://www.vtk.org/Wiki/Setting_up_a_ParaView_Server\&lt;/a&gt;) as rendering rendering speed isn't usually the bottleneck in visualisation using modern hardware ad it would be nice if the viz-paraview script could run in this way.  Perhaps it would be easiest to implement this when using GPUs exclusively, and then the user could specify how many pvserver instances to start per GPU although I suppose it could be implemented with shared GPUs as well.  As an illustration of the issue currently, to make use of all the CPU cores with viz-paraview on our system we would need to share each GPU six ways (12 core systems with two GPUs) which is less than ideal for other uses and in any case starting six X servers per GPU seems a bit excessive. It would seem to be more efficient to have a single X server per GPU and six pvserver instances all using the same X server for rendering.  I think this would be a nice addition to the already very useful script.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Tyson</dc:creator><pubDate>Wed, 23 Feb 2011 01:34:30 -0000</pubDate><guid>https://sourceforge.net257c511e3526eae1d324cab6bd0fab3920fd9130</guid></item><item><title>Need a mechanism to allocate specific resources</title><link>https://sourceforge.net/p/vizstack/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;VizStack scripts typically allocate resources as asked for by the user. Mechanisms are provided to ask for specific properties of the resources, e.g. a GPU capable of stereo, or a GPU on a specfiic node. However, there is no mechanism to allocate specific, known resources from scripts. &lt;/p&gt;
&lt;p&gt;The allocate function is very flexible and can allocate resources to meet many common criteria. Not all the flexibility is needed at the command line level.&lt;/p&gt;
&lt;p&gt;Two types of allocations seem to be of interest: allocating specific GPUs and allocating specific nodes. A mechanism is needed to make this possible.&lt;/p&gt;
&lt;p&gt;An interesting item to think about is : how will the additional resources be used ?these. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shree</dc:creator><pubDate>Wed, 25 Aug 2010 13:16:50 -0000</pubDate><guid>https://sourceforge.net9e944d295e15c27c2afe42eab99067aa7319f3d6</guid></item></channel></rss>