Server lag: Running 20215ms behind, skipping 404 tick(s)

Having the same issue

did this happen with things like enchanting tables and opening things like that

Doing anything. Placing/breaking blocks, running commands.. everything. There must be something that is taking up significantly more tick time in 14w02b than 1.7.4.
It wasn't quite as bad in 02a for me though

Same issue. Noticed that avg. tick when the world is loaded on server keeps increasing its value, getting above 300ms, and the server was acting like this also when I wasn't connected (launched server, went for a smoke, found this):

[21:21:03 WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 8478ms behind, skipping 169 tick(s)
[21:21:59 WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 47329ms behind, skipping 946 tick(s)
[21:22:10 WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 10572ms behind, skipping 211 tick(s)
[21:23:22 WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 61174ms behind, skipping 1223 tick(s)
[21:23:33 WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 11354ms behind, skipping 227 tick(s)

Singleplayer does more or less the same.

sadly with this bug i am unable to test the whole relative cords thing from the code by playing on the code 3 because well 14w02b ruins 1.7.4 worlds and adding they work fine when you rejoin them after converting back to 1.7.4

it seems its getting worse i can no longer play my new server with a 14w02c world

Do you have villagers?
I noticed ticks skip starts when my villagers at spawn go up to around 16-20, with more than 25 (ish) the block lag makes the world unplayable, until I kill some villagers to reduce population.

Some said it might be doors in the villages as well. MC-44531

I left all doors, just removed some villagers, still have 300 wooden doors at that place, but just 24 villagers.

that might be a bad thing considering i built a iron foundry on my world requiring lots of villages but it still affects all worlds

Java Version: 1.7.0_04, Oracle Corporation

Your Java version is out of date! Please update your Java to the latest version (1.7.0_51): http://www.java.com/en/download/.

• When using a 32-bit browser on a 64-bit operating system the automatic version detection will only show the 32-bit version of Java, the 64-bit version needs to be downloaded manually: http://www.java.com/en/download/manual.jsp.

Kumasasa that did not and does not help at all.

Please attach the complete output of the "Development console" which can be found on the second tab of the launcher.

If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open".

i had the crash report but your new system says i cant use that many charactars

So regarding the crash report, see that "Attachments" button? Yeah.

I cant get anything so show up in the crash report except running 2000 ms behind skipping 404 tick(s).

Crash report != server log

this no longer crashes the game but makes all 1.7.4 and below worlds unplayable in any 1.8 snapshots in the dev console I get the same message posted in the report above

I can confirm this. I started my server in 1.7.4. Not sure if that makes a difference but I'm noticing a lot of things from this such as picking up blocks that continue to appear on the ground (for me only) and the respawn button taking like 15 seconds to actually work.

Is this still a concern in the current Minecraft version 14w19a / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

this bug still applies to all 1.7.X worlds in all 1.8 snapshots

Running 1.8 vanilla server with 24 slots, 5 people online server CPU is maxed out and being 2004ms skipping ticks.

Server: Dual Quad Xeon 2.4 Cores with 8GB of memory. Memory sits at 50% usage but CPU is spiked.

use "nogui" with Server start script fixed the cant Keep up lagg on my Server

I've always used the nogui parameter yet I still have this problem with my server.

Attached file mс.txt
At the time of collection of information other server load is minimal. On the server two users: the first in the village, consisting of about 800 villagers, the second on the gold farm (48 portals maximum size). Both users in trolleys move around in their locations.

> 800 villagers.

Maybe that's your issue

No, not so. _Only_ 800 villagers on a server with Intel Xeon CPU E5-2640 @ 2.50GHz (24 ( ! ) cores), with 16G of memory allocated for minecraft. And such lags.

Also Minecraft 1.9

Two users logged in, one is about 1600,65,500 (the world is taking forever to load over a LAN connection); the other has coords less than 1000,xx,1000. Tick skipping has been going on all night, sometimes hitting the 60s threshold and shutting down the server.

My favorite is the last line, skipping 3.3 seconds about three seconds after it skipped 20 seconds.

Server 1.9, 2G of memory

[02:42:26] [Server thread/INFO]: There are 2/20 players online:
[02:42:26] [Server thread/INFO]: [player names redacted]
[02:42:34] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4008ms behind, skipping 80 tick(s)
[02:42:50] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3076ms behind, skipping 61 tick(s)
[02:43:08] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3887ms behind, skipping 77 tick(s)
[02:43:24] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3853ms behind, skipping 77 tick(s)
[02:43:41] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4159ms behind, skipping 83 tick(s)
[02:44:00] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5100ms behind, skipping 102 tick(s)
[02:44:16] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4823ms behind, skipping 96 tick(s)
[02:44:31] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3766ms behind, skipping 75 tick(s)
[02:44:49] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5604ms behind, skipping 112 tick(s)
[02:45:14] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 10619ms behind, skipping 212 tick(s)
[02:45:26] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 6139ms behind, skipping 122 tick(s)
[02:45:49] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 12556ms behind, skipping 251 tick(s)
[02:46:00] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5916ms behind, skipping 118 tick(s)
[02:46:40] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 19317ms behind, skipping 386 tick(s)
[02:46:43] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3382ms behind, skipping 67 tick(s)

1.9.3 confirmed

Can confirm 1.11

Can confirm 16w50a

Can confirm 1.11.1

Can confirm 1.11.2

Can confirm 18w21a.

will spam this error in the log when loading chunks

Can confirm for 1.13 pre1-8

I can confirmed on version 1.12.2.

I havea QUAD Xeons (4 PHYSICAL CPUS in my Dell Host) They are E7-4870's.

I am running ESXI 6.5 Update 2.

The VM has 16GB of RAM assigend to it and 6 cores (6x 2.4 GHZ).

I get lag spikes constantly.  And of course, the server can't keep up message.

How is this even possible. 

This is still an issue on 1.13.2, there have been no players connected to the server on the day of this output. The world has been generated on singleplayer (2 player LAN) on 1.13.2 and transferred to the server. The machine has a 2.2ghz core which makes the problem apparent straight away (doesn't matter how many cores I have, does it?)

There's no complex redstone circuitry or huge villages, we've only discovered about 4 villages in total actually. There's a high number of mobs around the spawn area (cows, chicken, sheep, maybe 100 total) and that's it. I don't even want to attempt to play on it anymore because we've died 2 times due to the server tick delays (surface drowned, then suffocated).

The game is unusable in its current state, unless it's intended for single player consumption, and LAN playing up to 4 players or so, and only on modern equipment (mid range desktop or high end laptop). 

• 2x Intel(R) Xeon(R) CPU L5630 @ 2.13GHz

• CentOS 7 64bit

• 16gb ram, 10 allocated to JVM

I'm not a mod, but this (generally) is a performance or (according to the wiki) an upload speed issue. About the hardware part, test the amount of entities in your server. I once had a bug in my server (vanilla that is) that prevented falling blocks from despawning, so i had arround 65,000 falling blocks that caused massive lag (skipped ticks). I recommend using the arguments described here and Java Oracle (or OpenJDK) version 11. Reduce the render distance on the server side and check for other processes consuming system resources. But I really have no idea how the powerful systems mentoned above can be insufficient. Unfortunately, I can't test for myself on a powerful system. With a void world though, there seems to be no problem at all, even when having many cmd blocks running. Also, I've read that minecraft servers before 1.14 have no mutlithread support. And in the case of the guy with the Xeon, I've seen (cpubenchmark.net) that the cores aren't that powerful.

We're closing this bug as it's a "catch-all"-bug that is essentially saying "server performance degraded for any reason".

If you have a specific case where server performance is bad, please search the bug tracker to see if you can find a bug that describes your issue and vote for it (or comment on it if the report is outdated and it's still happening).

If you can't find a bug that describes your problem, please create a new bug report.