<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Impact of large address group in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7708#M5697</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color:#333333;font-family:arial, helvetica, sans-serif;font-size:10pt;background-color:#f8fafd;padding-top:8px;padding-right:8px;padding-bottom:8px;padding-left:8px;text-align:left"&gt;What is the performance impact of having many addresses to match against?&amp;nbsp; If I have an address group that has hundreds of individual addresses in it (some FQDN), others ip netmask, will it have a noticible impact on performance?&amp;nbsp; We are using a 2050 primarily for URL filtering.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Aug 2011 16:41:06 GMT</pubDate>
    <dc:creator>Dshackelford</dc:creator>
    <dc:date>2011-08-18T16:41:06Z</dc:date>
    <item>
      <title>Impact of large address group</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7708#M5697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color:#333333;font-family:arial, helvetica, sans-serif;font-size:10pt;background-color:#f8fafd;padding-top:8px;padding-right:8px;padding-bottom:8px;padding-left:8px;text-align:left"&gt;What is the performance impact of having many addresses to match against?&amp;nbsp; If I have an address group that has hundreds of individual addresses in it (some FQDN), others ip netmask, will it have a noticible impact on performance?&amp;nbsp; We are using a 2050 primarily for URL filtering.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Aug 2011 16:41:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7708#M5697</guid>
      <dc:creator>Dshackelford</dc:creator>
      <dc:date>2011-08-18T16:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: Impact of large address group</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7709#M5698</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We do not have any published numbers for such a test case.&amp;nbsp; If possible try to use a subnet&amp;nbsp; to aggregate groups of devices and minimize the number of "look ups" that have to be made. But I think the impact will not be noticable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve Krall&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Aug 2011 17:12:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7709#M5698</guid>
      <dc:creator>skrall</dc:creator>
      <dc:date>2011-08-22T17:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: Impact of large address group</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7710#M5699</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In this case, the addresses cannot be represented by subnets or vlans as they are individual nodes across all our subnets and vlans.&amp;nbsp; I noticed in the config that there is a stated limit of 10,000 under config/devices/platform/limits but I also noticed that in the same area there is a limit of 500 addresses in an address-group.&amp;nbsp; I will take this as the practical limit for us.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Aug 2011 17:23:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/impact-of-large-address-group/m-p/7710#M5699</guid>
      <dc:creator>Dshackelford</dc:creator>
      <dc:date>2011-08-22T17:23:46Z</dc:date>
    </item>
  </channel>
</rss>

