Hello, I was poking around the different status pages on the gateway and noticed the load factor for all my devices is anywhere from 105% - 275% for “Scheduled at 1000ms”. There are close to 40,000 tags in my project and a majority of them run at a second scan class but I don’t see any performance…

If this is a CompactLogix or ControlLogix and you’re using a continuous task then check what the System Overhead Time Slice is currently set to. Moving from 20% to 40% or 50% can help a lot. If the CPU/comms usage for your Logix isn’t currently at or near max, then increasing the concurrent requests…

For sure. But I find that if I tell people it’s not going to happen, they’ll do the right thing and first think about whether they really need all their tags scanning at the rate they have them. When they’ve straightened that out, and are desperate, they’ll get their device to handle more requests a…

Thanks for the responses. I have never done the drag-and-drop thing and most come from instances of data types. I recently moved about a quarter of them to leased scan classes. Based on your recommendations I’ll be taking a much closer look at the others. To make sure I understand correctly, thi…

I have also experienced some random delays in my tag updates by seeing the Uncertain / Unknown quality overlay. Adding to Kevin’s post, if you are using Periodic Tasks and have the time (period) set to a value close to the actual scan time of the task, then that task will consume much of the CPU, l…

Hi all, I’ve tried the optimizations listed on this page and my device load did drop from over 100% to somewhere between 25-45%, however I notice the load factor go up sometimes as I am pressing buttons quickly to about 50-70%. I have a total of around 7000 tags, with my leased scan class being 1 …

Wish I’d seen this suggestion a long time ago. I have an L71 which is doing very little work and even polling 130 tags at 500ms was unusable. I changed the system overhead time slice from 20% to 50% and my device load went from 300% to 17% Not only that, but studio 5000 online edits are much fast…

Bringing this thread back to life because we recently set up a new Ignition server (new server hardware) to replace the current server. We have been running the new server in parallel with the old server and out of the 23 PLCs connected, only 1 LogixDriver has a high load (2 other LogixDriver PLCs …

Your mean response times are astonishingly bad. Logix processors usually respond in single-digit milliseconds. For starters, make sure the PLC does not have a continuous task – convert it to a periodic task with the longest practical interval for your process.

I’m happy to report that changing the continuous task to periodic at even 125ms has brought the device load factor down tremendously. Thanks Phil. [LoadFactorNormal]

Hi Mbhagotra… was browsing around and noticed your post. For me, using a prime number based timing scheme seemed to really get the most out of my throughput and efficiency. For instance, if you have scan classes set up at 500ms, 1000ms, 2000ms and 10000ms, then you are causing these to frequently …

Inductive Automation Forum

Device Load Factor

Ignition

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled