I've tested it with only RC on 1.10.2. I love how it adds trees and makes the terrain teeming with life. but every time I load new chunks and break blocks, they don't properly drop. Not FPS lag, having some block and chat lag.

I don't remember any of those on 1.7 version. What happened? IS there ways to have better performance? Are you guys working on it?

3,5G given to mc.

Try using the profiler to see what's causing the lag.
Either the world generator is still running - in that case you can just sit back and wait a bit for it to complete.
It might also be that you have lots of decaying leaves - a lot of people prefer to change the config option treeLeavesDecay to false. This will of course only work on new worlds.

http://pastebin.com/zw16fqek
http://pastebin.com/KeGHnYFZ

I believe i might be having the same issue here.

Seems to be related to tree growth?

Only problem is I have to convince the other 30 or so devs making mods for my pack of the same thing.

Are there that many mods not being updated yet? I'm honestly surprised. Looking across curse I don't see many out of date myself.

Try the latest nightly - the problem should either be gone or greatly reduced.

Will do as soon as I'm in a spot I can.

@Ivorforce tried the 1.10.2 1.2.4 version, still bad. It might be worse in performance and broken blocks not popping up. Also are you going to support 1.10.2, halted support or it magicaly supports 1.10 from 1.11 versions with that mcjts mod?

The changes were made purely in the 1.11 nightly builds. A release will be available soon, but not for 1.10.

but its too early to remove support from 1.10.2
:L

1.11 is not a very big update. It shouldn't be hard to update to it from 1.10.

Let's see. It's not quite 30 mods, I don't think, but I have some automation for this... https://github.com/TPPIC/Test-Factory-Please-Ignore/blob/1.11/MODS.md

(Ignore the "1.10" line, the code writing MODS.md has no idea that I asked for 1.11 versions this time around.)

So that's... 56 mods.

Right. Welp. It's not 30.

I'll close this for now as the issue itself should be resolved. A backport of this feature is a different question to be discussed in a new issue. In case it persists in 1.11 latest, please reopen this issue.