Createseems to use an ungodly amount of bandwidth
Gartral opened this issue ยท 2 comments
Describe the Bug
while create machines are running, users receive 1-2 megabits per second from the server, causing lag for servers on low-upload bandwidth connections.
Reproduction Steps
- Set up server with create
- build a moderately complicated contraption
- watch bandwidth with iftop or glasswire or similar
- see high network per client
...
Expected Result
The usual amount of bandwidth used by modded minecraft is an order of magnitude less than with create contraptions running. Even just stopping the machines in world brings the client bandwidth usage back down to 100-200 kilobytes per second.
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Ubuntu 22.04 server, various clients, including linux and mac
Mod Version
0.5.0g
Minecraft Version
1.19.2
Other Mods
AE2WTLib-12.8.4.jar
appliedenergistics2-fabric-12.9.2.jar
comforts-fabric-6.0.3+1.19.2.jar
ferritecore-5.1.0-fabric.jar
resourcefulconfig-fabric-1.19.2-1.0.18.jar
Chunky-1.3.38.jar
architects-palette-fabric-2.1.1.jar
conjuring-1.0.26+1.19.jar
godown-0.3.0+1.19.jar
resourcefullib-1.1.20.jar
Continents_1.19_v1.1.1.jar
architectury-6.4.62-fabric.jar
convenient-mobgriefing-2.0.2.jar
hexcasting-fabric-1.19.2-0.10.3.jar
show-me-your-skin-1.3.4+1.19.jar
DramaticDoors-Fabric-1.19.2-1.3.5_1.jar
autoconfig1u-3.4.0.jar
create-fabric-0.5.0.i-946+1.19.2.jar
immersive_aircraft-0.3.0+1.19.2-fabric.jar
spark-1.9.42-fabric.jar
Incendium_v5.1.3a.jar
badpackets-fabric-0.2.1.jar
discord4fabric-1.19.2-1.10.1.jar
infusion-table-mod-1.1.0.jar
starlight-1.1.1+fabric.ae22326.jar
InvView-1.4.9-1.19+.jar
bewitchment-1.19-6.jar
dustrial-decor-fabric-0.5.jar
krypton-0.2.1.jar
supplementaries-1.19.2-2.2.30-fabric.jar
LuckPerms-Fabric-5.4.57.jar
bitsandchisels-2.7.0.jar
emi-0.4.2+1.19.jar
light-overlay-7.0.0.jar
textile_backup-2.4.0-1.19.1.jar
NoChatReports-FABRIC-1.19.2-v1.13.12.jar
blockus-2.5.6+1.19.2.jar
emicompat-2.0.1.jar
lithium-fabric-mc1.19.2-0.10.2.jar
trinkets-3.4.1.jar
Nullscape_v1.2a.jar
botarium-fabric-1.19.2-1.8.2.jar
extra-generators-1.2.1-BETA+1.19.jar
wired-redstone-0.4.14+1.19.2.jar
Origins-1.19.2-1.7.1.jar
c2me-fabric-mc1.19.2-0.2.0+alpha.9.0.jar
extraorigins-1.19-2.jar
moonlight-1.19.2-2.1.21-fabric.jar
wirelessnetworks-1.6.0.jar
Patchouli-1.19.2-77-FABRIC.jar
cardinal-components-api-5.0.2.jar
fabric-api-0.73.2+1.19.2.jar
notenoughcrashes-4.2.1+1.19.2-fabric.jar
worldedit-mod-7.2.12.jar
Pehkui-3.6.0+1.14.4-1.19.3.jar
cc-restitched-1.101.2.jar
fabric-carpet-1.19.2-1.4.84+v221018.jar
owo-lib-0.9.3+1.19.jar
wraith-waystones-3.0.5+mc1.19.2.jar
Terralith_v2.3.4.jar
charm-fabric-1.19.2-4.4.4.jar
fabric-language-kotlin-1.8.7+kotlin.1.7.22.jar paucal-fabric-1.19.2-0.5.0.jar
wthit-fabric-5.13.4.jar
ad_astra-fabric-1.19.2-1.12.2.jar
cloth-config-8.2.88-fabric.jar
fabric-language-kotlin-1.9.0+kotlin.1.8.0.jar
polymorph-fabric-0.46.1+1.19.2.jar
xp_obelisk-0.4.7-r+1.19.2-Fabric.jar
Additional Context
No response
Well, we've identified the misbehaving component as the fluid pipes, we have a workaround with AE2's fluid logistics system. If there's any testing that needs to be done to confirm this I suggest using iftop on the host and setting up a pipe network and watcxhing the realtime network traffic.
further tools might help