# Ignition & Logix Best Practice Tips for better communications **URL:** \ **Category:** Ignition\ **Tags:** rockwell\ **Created:** [June 5, 2022, 11:46pm UTC](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386 "2022-06-05T23:46:38Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![A\_Power](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@A\_Power](https://forum.inductiveautomation.com/u/A_Power)\ **Post date:** [September 28, 2022, 2:21am UTC](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386/16 "2022-09-28T02:21:54Z")
So quick update for those of you playing from home. A colleague has just pointed out something I myself missed completely. Max Concurrent Requests (OPC Device Settings) - by default is 2. We just upped ours to 4 The problems we were having went away. Load went right down in ignition by 80%, and by about 30% on our PLC I see this has been mentioned before back in the day by @pturmel > [@Tag Scan Class](https://forum.inductiveautomation.com/t/tag-scan-class/11712/12): > > Increase the max concurrent requests. I suggest 8 or 10. (I think the max is 12, but don’t quote me on that.) The problem is that with only 2 requests at a time, and hundreds of requests needed per scan, round-trip travel and process time suddenly becomes significant. If it’s still not enough, you can create multiple drivers to the same processor to get more concurrency. Before I go screaming it's fixed and summarizing these findings, is there any healthy Convo to be had around this? What to do or what to check before you play with this number? Times when it is not a good idea and could have negative outcomes? But yeah I am buying someone a beer... You don't know until you know! --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386)._