I've been relying heavily on the universal properties of Mekanism's Universal Cables for just about all of my power transferring needs, until today.
For the past three days or so my VPS provider has been having a few CPU issues (probably node abuse again). This prompted me to seek out any and all inefficient systems in an attempt to curb my server's cpu usage. Upon running a ps aux command I noticed that over the last week my cpu usage has shot up sixty percent from forty percent with server tickrate suffering greatly.
I ran Opis for a while, it of course identified only a single laggy chunk. That's pretty good for a base that encompass well over fifty chunks..
I've heard some bad things about UE cables being pretty demanding but, I hadn't had the time to switch my entire system over to conduits. That problem has now been remedied. After swapping out my UE cables for Redstone Energy Conduits, server cpu usage dropped by over twenty five percent. That's a staggering amount of CPU usage for a power network that was only going to grow larger.
Has anyone else experienced this while using UE Cables? Here I thought large arrays of Buildcraft pipes/EnderIO conduits were bad..
I'm using the latest developer build obtainable on the Mekanism Jenkins for version 1.6.4.
For anyone else running into issues with large power networks, this setup works flawlessly.
http://i.imgur.com/7vW7scd.png
When dealing with all non RF/MJ consuming machines you are still able to use the processor friendly Redstone Energy Conduits. I have thousands of these conduits spread out throughout my base. As if we needed further proof of King Lemming's ability to optimize.
For the past three days or so my VPS provider has been having a few CPU issues (probably node abuse again). This prompted me to seek out any and all inefficient systems in an attempt to curb my server's cpu usage. Upon running a ps aux command I noticed that over the last week my cpu usage has shot up sixty percent from forty percent with server tickrate suffering greatly.
I ran Opis for a while, it of course identified only a single laggy chunk. That's pretty good for a base that encompass well over fifty chunks..
I've heard some bad things about UE cables being pretty demanding but, I hadn't had the time to switch my entire system over to conduits. That problem has now been remedied. After swapping out my UE cables for Redstone Energy Conduits, server cpu usage dropped by over twenty five percent. That's a staggering amount of CPU usage for a power network that was only going to grow larger.
Has anyone else experienced this while using UE Cables? Here I thought large arrays of Buildcraft pipes/EnderIO conduits were bad..
I'm using the latest developer build obtainable on the Mekanism Jenkins for version 1.6.4.
For anyone else running into issues with large power networks, this setup works flawlessly.
http://i.imgur.com/7vW7scd.png
When dealing with all non RF/MJ consuming machines you are still able to use the processor friendly Redstone Energy Conduits. I have thousands of these conduits spread out throughout my base. As if we needed further proof of King Lemming's ability to optimize.