Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Suggestion: Make piston multi-threaded #75

Open
Kyrobi opened this issue Mar 23, 2019 · 3 comments
Open

Suggestion: Make piston multi-threaded #75

Kyrobi opened this issue Mar 23, 2019 · 3 comments
Labels
accepted True. enhancement New feature or request future Not now. we need go deeper We need go deeper!
Milestone

Comments

@Kyrobi
Copy link

Kyrobi commented Mar 23, 2019

I was interested in testing how pistons affects the server since tile ticks are multi-threaded. I placed down ~700 pistons and hooked them up to a clock using observers.

When doing the testing, I noticed that a single core was at ~100% usage while others are basically idle. Would it be possible to make pistons / observer multi-threaded, or am I doing something wrong?

Edit: I don't know if it's the observer solely that's contributing to the lag, the pistons, or both :/

@shinohara-rin
Copy link
Member

it's possible, but likely to cause chunk synchronization problems. implementing such asynchronous mechanism would be painful and would leads to tons of bugs. we haven't found a practical way to solve this issue currently...

@shinohara-rin shinohara-rin added the future Not now. label Mar 23, 2019
@cakoyo cakoyo added the enhancement New feature or request label Mar 23, 2019
@cakoyo cakoyo added this to the Fast milestone Apr 3, 2019
@WhyDoWeWonder
Copy link

If pistons and/or redstone are causing a lot of lag try using an alternative redstone algorithm, which can often reduce related types of lag by up to a factor of 20. If you need some help with setting one up or choosing one please respond.

@josephworks josephworks added we need go deeper We need go deeper! accepted True. labels May 6, 2020
@josephworks
Copy link
Member

bump.
We should do this

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
accepted True. enhancement New feature or request future Not now. we need go deeper We need go deeper!
Projects
None yet
Development

No branches or pull requests

5 participants