Tekkit Creative?
- th3thrilld3m0n
- Architect
- Contact:
- CPU: Artificial Intelligence
- RAM: 9001 TB
- Motherboard: Your Mother
- Display: IMAX 3D
- Cooling: Fire
- Location: TARDIS
Post
Re: Tekkit Creative?
just remember to always save some CPU and RAM for the OS or, from friend's experience, it will say (Mac) "Stop stealing Macintosh!", basically, make sure you leave enough for the OS or else u get no comp.
Signature
YouTube: http://www.youtube.com/user/th3thrilld3m0n
Twitter: http://twitter.com/th3thrilld3m0n
Tumblr: http://th3thrilld3m0n.tumblr.com/
Soundcloud: http://soundcloud.com/th3thrilld3m0n
YouTube: http://www.youtube.com/user/th3thrilld3m0n
Twitter: http://twitter.com/th3thrilld3m0n
Tumblr: http://th3thrilld3m0n.tumblr.com/
Soundcloud: http://soundcloud.com/th3thrilld3m0n
- CraftminerX
- Member
- CPU: Junk.
- RAM: 4 GB Corsair DDR2
- Motherboard: Also junk.
- GPU: 1x NVidia GeForce 8800GT 512MB
- Display: 1x 24" Acer
- Cooling: Air
- Location: Behind you.
Post
I'm surprised Bukkit doesn't have multi-threading functionality. (Although it wouldn't be that easy to implement...)
Re: Tekkit Creative?
Minecraft servers are single-threaded? :OPri wrote:I really don't see me changing my mind on this until the server software becomes multithreaded. Sorry.
I'm surprised Bukkit doesn't have multi-threading functionality. (Although it wouldn't be that easy to implement...)
- Pri
- Site Admin
Post
Re: Tekkit Creative?
Some parts of the server are multithreaded but not in the way it should be.
Basically they multithreaded things in a very cheap way. You have the main thread which the majority of stuff runs under but then you have extra threads to handle things like in-game chat and server-player communication. The main thread still handles the meat of the game though and a single process (like reading or writing to the disk) is not multithreaded and runs inside that main thread.
So this means if you're creating or destroying thousands of blocks the disk access is locking that main thread. We have an SSD and use MySQL with a large RAM cache to mitigate these issues but it is no where near enough. When I looked at the database just within a 5 minute time frame over 250,000 blocks are being created or destroyed. 99% of that by automated machines like condensers which we have since nerfed by limiting them to one per player.
But really the server needs to be fully multi-threaded and only Mojang can do that. Bukkit can't do it.
Basically they multithreaded things in a very cheap way. You have the main thread which the majority of stuff runs under but then you have extra threads to handle things like in-game chat and server-player communication. The main thread still handles the meat of the game though and a single process (like reading or writing to the disk) is not multithreaded and runs inside that main thread.
So this means if you're creating or destroying thousands of blocks the disk access is locking that main thread. We have an SSD and use MySQL with a large RAM cache to mitigate these issues but it is no where near enough. When I looked at the database just within a 5 minute time frame over 250,000 blocks are being created or destroyed. 99% of that by automated machines like condensers which we have since nerfed by limiting them to one per player.
But really the server needs to be fully multi-threaded and only Mojang can do that. Bukkit can't do it.
Return to “Minecraft General Discussion”
Who is online
Users browsing this forum: No registered users and 4 guests