https://community.esri.com/t5/arcgis-pro-ideas/arcgis-pro-3-4-system-requirements-network-speed/idi-p/1556668 <P>Add network speed to the metrics of determining system suitability for ArcGIS Pro.</P> <P>Good practice is to save data and work product in a location that is backed up and resilient.&nbsp;</P> <P>Pro is sensitive to network performance, both from a speed and latency point of view.</P> <P>With Wifi now at a 7th generation level, speeds (marketing?) are approaching a traditional wired paradigm.</P> <P>There are also still companies that have users share VOIP phones and a data connection on a single gigabit port - meaning that the computer may end up with a 100mbit connection (in 2024!!!).</P> <P>Add a component to the System Requirements and checker to include a basic network spec. and measure a few basic metrics to set a realistic expectation of performance and responsiveness.</P> <P>WiFi should be measured against an ideal throughput and latency rather than a spec as there are so many variables involved.</P> <P>Further to this - re-write the specifications to be framed as a justification. These will often be used in budget discussions and having an 'independent' "Why" will support your users more than just saying your system is a Pass.</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RTPL_AU_0-1731024509349.png" style="width: 400px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/119114iA1D17887486EB18F/image-size/medium?v=v2&amp;px=400" role="button" title="RTPL_AU_0-1731024509349.png" alt="RTPL_AU_0-1731024509349.png" /></span></P> <P>&nbsp;</P> <P>Brownie Points:</P> <P>Add a score to each component based on its impact on Pro performance and responsiveness.<BR />This should cover local data, network data, (raster or vector), and UI responsiveness. Include use cases such as visual complex cartography vs hardcore arcpy number crunching.<BR /><BR />Add the ability to type in system components to see what the impact is on the score.&nbsp; If you don't have the hardware yet how are you going to run the checker?</P> <P>Add the ability to export this as an Esri-branded document to include in a budget justification. (i.e. put your brand where your mouth is).<BR /><BR />I see this all as a purely busy-work supporting activity to help GIS teams justify expenditure to ill-informed organisations, as the truth is that Pro performance is a much more complex issue than just saying get a Threadripper Pro + 4090 and you'll be good.&nbsp;</P> <P>&nbsp;</P> <P>&nbsp;</P> Fri, 08 Nov 2024 13:43:57 GMT RTPL_AU 2024-11-08T13:43:57Z https://community.esri.com/t5/arcgis-pro-ideas/arcgis-pro-3-4-system-requirements-network-speed/idi-p/1556668 <P>Add network speed to the metrics of determining system suitability for ArcGIS Pro.</P> <P>Good practice is to save data and work product in a location that is backed up and resilient.&nbsp;</P> <P>Pro is sensitive to network performance, both from a speed and latency point of view.</P> <P>With Wifi now at a 7th generation level, speeds (marketing?) are approaching a traditional wired paradigm.</P> <P>There are also still companies that have users share VOIP phones and a data connection on a single gigabit port - meaning that the computer may end up with a 100mbit connection (in 2024!!!).</P> <P>Add a component to the System Requirements and checker to include a basic network spec. and measure a few basic metrics to set a realistic expectation of performance and responsiveness.</P> <P>WiFi should be measured against an ideal throughput and latency rather than a spec as there are so many variables involved.</P> <P>Further to this - re-write the specifications to be framed as a justification. These will often be used in budget discussions and having an 'independent' "Why" will support your users more than just saying your system is a Pass.</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RTPL_AU_0-1731024509349.png" style="width: 400px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/119114iA1D17887486EB18F/image-size/medium?v=v2&amp;px=400" role="button" title="RTPL_AU_0-1731024509349.png" alt="RTPL_AU_0-1731024509349.png" /></span></P> <P>&nbsp;</P> <P>Brownie Points:</P> <P>Add a score to each component based on its impact on Pro performance and responsiveness.<BR />This should cover local data, network data, (raster or vector), and UI responsiveness. Include use cases such as visual complex cartography vs hardcore arcpy number crunching.<BR /><BR />Add the ability to type in system components to see what the impact is on the score.&nbsp; If you don't have the hardware yet how are you going to run the checker?</P> <P>Add the ability to export this as an Esri-branded document to include in a budget justification. (i.e. put your brand where your mouth is).<BR /><BR />I see this all as a purely busy-work supporting activity to help GIS teams justify expenditure to ill-informed organisations, as the truth is that Pro performance is a much more complex issue than just saying get a Threadripper Pro + 4090 and you'll be good.&nbsp;</P> <P>&nbsp;</P> <P>&nbsp;</P> Fri, 08 Nov 2024 13:43:57 GMT https://community.esri.com/t5/arcgis-pro-ideas/arcgis-pro-3-4-system-requirements-network-speed/idi-p/1556668 RTPL_AU 2024-11-08T13:43:57Z