Big Reactors

Big Reactors

11M Downloads

Major lag and drop of server TPS.

DrC0ns0le opened this issue · 7 comments

commented

I built a 5X5 reactor using Direwolf20 pack.I have two redstone port and they are used to turn the reactor on and off.One redstone port sends redstone signal when the internal buffer is below 50% and the another one will turn the reactor on when it receives a redstone signal.When the reactors turn on it lag and server TPS went from 20 to 13-15 tps.

====http://imgur.com/a/dKIWX=====
========Picture of reactor.=======

==============Video showing tps drop when reactor turning on or off.======================
=====https://www.youtube.com/watch?v=G443zkAhBGc&list=UUV86gq2QlGIA-GW3vAAkyHA=====

Will upload world save file.

commented

Direwolf20 FTB Pack ver. 1.0.1

commented

I'm getting a file-not-found error when trying to view the screenshot.

What's strange is that, at the end of that video, the reactor turns on, and yet the TPS doesn't drop. What's your redstone setup like? What sort of redstone transport are you using? (Vanilla redstone, rednet wire, EnderIO cables?) Can I get some screenshots of that?

commented

Hm. Does this also happen without the redstone ports? I'm suspecting redstone hysteresis leading to a flood of update packets.

commented

@erogenousbeef The file not found error is because of the ===== after wards. http://imgur.com/a/dKIWX Actual link.

commented

On Nov 24, 2014, at 5:03 AM, Mr. E. Beef [email protected] wrote:

Hm. Does this also happen without the redstone ports? I'm suspecting redstone hysteresis leading to a flood of update packets.


Reply to this email directly or view it on GitHub #389 (comment).

No,it doesn’t happen when I turn it on or off manually.=

commented

All right. The problem is almost certainly that the reactor is flipping itself on and off once per tick, resulting in a flood of updates.

If you want a server-side throttle, you can increase the ticksPerRedstoneUpdate setting ("General" section). This will slow down the rate at which redstone ports respond to changes in the reactor's state, which means the reactor will spend more time between flipping on and off.

However, one major problem is with the redstone setup itself.

Essentially, if you have a power draw, your reactor's power buffer will fill up to 50%, then switch off, drop immediately to 49% and switch on again. You'll need to devise a way to switch off when the buffer approaches full, and switch on again when the buffer is empty. Any additional throttling in the BR code itself would only be a band-aid over this.

However, I'll poke around and see if I can optimize reactor state changes. The updates certainly shouldn't be so heavy that they kill a server.

commented

I will definitely fix my redstone problem and at least my stupidity helped to discover something!