# SLC500 Communication Best Practices

**URL:** <https://forum.inductiveautomation.com/t/slc500-communication-best-practices/33285>\
**Category:** General Discussion\
**Created:** [March 20, 2020, 9:33pm UTC](https://forum.inductiveautomation.com/t/slc500-communication-best-practices/33285 "2020-03-20T21:33:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 20, 2020, 9:38pm UTC](https://forum.inductiveautomation.com/t/slc500-communication-best-practices/33285/2 "2020-03-20T21:38:39Z")

</div>

Best advice I've seen on here is from @pturmel:

> [@Typical Performance between Ignition and AB SLC 5/05](http://forum.inductiveautomation.com/t/typical-performance-between-ignition-and-ab-slc-5-05/17262/3):
>
> Check “Comms Servicing Selection” and “MSG Servicing Selection” for channel 1 (S:2/15 & S:33/7). If either is set, it will crush your throughput, as only one request will be processed per scan (Comms) or per certain control flow instructions (MSG).

We don't have any guide. These things are old and slow, so only create tags for the data you need at as slow a rate as you can tolerate. Some people used leased scan classes to speed things up when tags are visible on a screen but disable or slow them down otherwise.

---

_[View the full topic](https://forum.inductiveautomation.com/t/slc500-communication-best-practices/33285)._