Daniel Chehade

I don't know why but it's like 1.8 has fudged-up my CPU. Before 1.8 came out I played with like 500+ FPS, now in 1.8 I got like 70-90 with 16 chunks. Then I played alpha, beta and pre-alpha version and I "low" fps there as well! Here's all versions average FPS (for me): Dev-version: 290 Pre-alpha: 210 Alpha: 160 Beta: 120 Release (1.4-1.7.10): 90. And I'm not exaggerating... Just me using a beast... Well, it WAS a beast until 1.8 destroyed it...
When I played for example pre-alpha before I would get a average FPS of 3000 and on Dev versions I would get like 4800!!! Thanks alot, Mojang!!
What I am trying to say: It's like 1.8 has "degraded" and "destroyed" my CPU...

Specs:
CPU: i7 4770k OC (4.3Ghz - I've tested on stock speed too, slower...)
GPU: MSI GTX 770
RAM: Corsair Vengeance 16GB 2133Mhz Quad Channel
SSD: Samsung 256GB Desktop Kit
PSU: Corsair RM 850W Gold 80+ Modular

@unknownYeah, sure, your right (and I forgot about it...). But your going overboard, do you really think TMI makes me lag?? And TMI doesn't make ANY DIFFERENCE WITH AN I7 4770K AND AN GTX770!!! USE your head... You got it for a reason.... Just saying, everybody here is saying the same issue, lag... So if I use TMI and still report lag don't you think it's the same as everybody else?? And I've already tested without it...

@unknown That IS the vanilla Minecraft... If you look at the icon on the taskbar you see the minecraft icon... and it SAYS 1.8...

Found the issue!! By my experience, it's not the water nor the lightning. It's the chunk renderer/updater. Noticed if I dig down 1 or 2 blocks and look down the chunk updates goes from 600 to 1 and by then I got 750 Fps. So somethings wrong with the chunk rendering. I beg of Mojang/Microsoft to have a look at this please... Well, I could be wrong but still, a chunk renderer that updates 500-800 chunks is plausible... And the same goes for the chunk updater itself.
EDIT: Here's a video if you still don't get it: http://youtu.be/XKt-p4RwlpY

@Christopher_Andthatsit Oh, now I understand. But I spelled wrong with the "at my" part. I think I mean't "that my" =3
And for the 3:rd part (render distance theory). Yes, that would be an excellent idea. But Mojang doesn't give a duck about bugs like these... I think VBOs was successful but something is interfering WITH the VBOs feature! That's my theory!

Nice! Now I get 700-800 Fps in 1.8 with lowest on and render distance on 6 but I still get those Micro Freezes... I think the mojang team was drunk when they coded this...
EDIT: Now I see... When I turn everything to max except for the render distance (still at 6) I get almost same fps...The render distance, there's 1.8's problem! Wrong coded or something I think!
EDIT 2: Lol, can play 1.8 now! All you have to do is have everything at whatever you want but render distance at 5 or under (Then I get little to very little micro freezes). Other settings doesn't matter! Only render distance that's ducked up!

Can confirm that Java 7 makes me get micro-freezes 24/7 but more FPS.

@Alex_McNeil So true . From now on I will hate Haswell cpu's...
@Christopher_Andthatsit Huh??

Me back, I had 500 FPS BEFORE 1.8 came out, then I got 30- Fps and get micro freezes. Then I switch back to 1.7.10 And still has that 1.8 lag bullshit... And the servers lag shit with me having 100/10 network speed... Java 8 update 20 64 bit and JDK 64 bit. Intel Core i7 4770k, GTX 770 and 16GB Ram 2133Mhz... At my computer sucks? Or the game that got 250% slower?

Me again, just noticed that my CPU seems half broken so that 1 reason my FPS went down from 500 to 100 in 1.7.10 (When I switched back) and my temps go up from 35 to 56 when I play minecraft! Just sayin' that 20% of the people might have lag like this because of hardware issues! Like me =(

Confirmed in 1.8 (Release) too!

Hate this bug :l

Now that 1.8 came out I ran home and wanted to play it. Then I downloaded then update and immediately started my single player world. When I run on lowest i get 60 FPS but when I just higher that by a little bit I get 1-6 FPS... And in 1.7.10 with highest settings I got 400 FPS average...
Specs: Intel i7 4770k, GTX 770, 16GB Ram... So shouldn't 1.8 "BOOST" the performance, especially with VBOs....
EDIT: Well, actually, now when I allocated 512MB Ram (Xms java flag) and dedicated 4GB (Xmx java flag) it works alot better now when under 16 render distance... So I'd recommend that you (Mojang) work on the render distance fps drop bug.

Oh yeah, sorry, when i saw the console it said:
[21:54:35 INFO]: Client> [21:54:35] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 10342ms behind, skipping 206 tick(s)
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.level.chunkCache.recheckGaps' took aprox 369.447287 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/INFO]: Warning: Clientside chunk ticking took 372 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.level.chunkCache' took aprox 372.168152 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.level' took aprox 373.516901 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 374.666463 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root' took aprox 390.020246 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.level.chunkCache.recheckGaps' took aprox 366.16829 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/INFO]: Warning: Clientside chunk ticking took 368 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.level.chunkCache' took aprox 367.605827 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.level' took aprox 368.559414 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 456.748596 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root' took aprox 475.095154 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick.gameMode' took aprox 115.818981 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 129.992535 ms
[21:54:36 INFO]: Client> [21:54:36] [Client thread/WARN]: Something's taking too long! 'root' took aprox 146.965226 ms