<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[&quot;Max Clients&quot; value for storage with multicast connections wrong]]></title><description><![CDATA[<p dir="auto">Hey there,</p>
<p dir="auto">when using multicast download there should be only one connection to the storage node. Unfortunately, the node uses slots for each multicast client. So you have to massively turn op the number of allowed connections when using a lot of multicast, which can decrease the perfomance when a lot of unicast connections get established.</p>
<p dir="auto">It would be great if multicasts get somehow grouped together als single tasks. This would also make the task view look way more clear.</p>
]]></description><link>http://forums.fogproject.org/topic/3488/max-clients-value-for-storage-with-multicast-connections-wrong</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Mar 2026 09:17:05 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/3488.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 Jul 2014 14:16:38 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to &quot;Max Clients&quot; value for storage with multicast connections wrong on Mon, 21 Jul 2014 14:19:52 GMT]]></title><description><![CDATA[<p dir="auto">Um what?  Multicast tasks take no slots on the queue as is designed.  While you may see a task for every host this is to be expected otherwise how will the system know which clients you’re trying to multicast too?</p>
]]></description><link>http://forums.fogproject.org/post/27298</link><guid isPermaLink="true">http://forums.fogproject.org/post/27298</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Mon, 21 Jul 2014 14:19:52 GMT</pubDate></item></channel></rss>