# Network and Bandwidth recommendations for stable Ignition

**URL:** <https://forum.inductiveautomation.com/t/network-and-bandwidth-recommendations-for-stable-ignition/59236>\
**Category:** Ignition\
**Tags:** ignition80, ignition81, perspective\
**Created:** [May 5, 2022, 6:48am UTC](https://forum.inductiveautomation.com/t/network-and-bandwidth-recommendations-for-stable-ignition/59236 "2022-05-05T06:48:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hayden](https://avatars.discourse-cdn.com/v4/letter/h/91b2a8/32.png) [@hayden](https://forum.inductiveautomation.com/u/hayden)\
**Post date:** [May 5, 2022, 6:48am UTC](https://forum.inductiveautomation.com/t/network-and-bandwidth-recommendations-for-stable-ignition/59236/1 "2022-05-05T06:48:37Z")

</div>

Hey all,

We’ve been trying to test and prepare to implement an Ignition project to replace our clients old system. A major hurdle in this though is their aging network infrastructure. This network is spread across several locations using old modems, serial connections/converters and some Ethernet connections almost all of it around 20/30 years old.

To get all of our sites connected to our central server we’ll need to use this aging infrastructure as fully replacing it is not practical.

Our current project spec should contain around 50 DNP3 device connections each wit around 100/200 tags, connecting to a server and then using browser based perspective sessions (clients request).

We tried a smaller demo system and had some issues with connectivity which we are working out. I’m in the process of logging and estimating this systems network load.

Is there a recommended bandwidth and network speed for Ignition to function effectively. We’ll probably go for some kind of ‘scale-up’ architecture to try and reduce network load.

Thanks

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [May 5, 2022, 12:03pm UTC](https://forum.inductiveautomation.com/t/network-and-bandwidth-recommendations-for-stable-ignition/59236/2 "2022-05-05T12:03:31Z")

</div>

Have you looked into using MQTT between the locations? It’s a lot more efficient in low bandwidth environments.

---

<div class="post-metadata">

**Author:** ![hayden](https://avatars.discourse-cdn.com/v4/letter/h/91b2a8/32.png) [@hayden](https://forum.inductiveautomation.com/u/hayden)\
**Post date:** [May 6, 2022, 12:24am UTC](https://forum.inductiveautomation.com/t/network-and-bandwidth-recommendations-for-stable-ignition/59236/3 "2022-05-06T00:24:10Z")

</div>

We’d looked into it, and use it on other projects. Unfortunately for this project DNP3 is a requirement set by our client.

---

<div class="post-metadata">

**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\
**Post date:** [May 6, 2022, 3:47am UTC](https://forum.inductiveautomation.com/t/network-and-bandwidth-recommendations-for-stable-ignition/59236/4 "2022-05-06T03:47:46Z")

</div>

Ignition edge at all remote locations (if your project can afford 50 of them) will enable dnp connection as well could act as remote tag providers with central Ignition server in addition it could also act as local HMI and connect with your existing infrastructure thru OPC or MODBUS or whatever possibility you have in your existing infrastructure.