The short time I messed with it, both cores of my CPU were more or less maxed, while my GPU was hardly being used. Considering cpu is pretty much the weakest link on my old system, in it's current state I will be sticking with 1.7.10 and earlier. Pretty much bored with vanilla anyway, so would've been a while before I moved ahead.
The weird thing for me is that I only have a 2.2 GHz dual-core AMD Athlon 64 X2 and it doesn't max out either core, which suggests the bottleneck is something else; the spikes do seem to correspond to lag spikes in-game but I never saw it go above 80%:
For comparison, this is while running 1.6.4, which uses near 100% CPU all the time (split about 3:1 between the javaw and dwm processes, which presumably updates the display), but doesn't lag, so it appears that something is preventing 1.8 from efficiently utilizing the CPU:
Perhaps it is the extreme memory bandwidth used by 1.8, as seen by watching the memory usage, which rises at an extremely fast rate, several hundred MB per second (also mentioned in this thread), before rolling over and repeating the cycle; memory usage in 1.6.4 only increases by a few MB per second. 400 MHz DDR RAM should be able to sustain those rates though.
Most interesting is what happens when I turn Advanced OpenGL off in 1.6.4 (which was removed due to issues in 1.8, also causes occasional invisible chunk sections in 1.6.4 but Optifine fixes it):
This also drops average FPS by about half, but still entirely playable, around 40-50 FPS on Normal and Fast, with some lag when turning around in windowed mode, but the lag appears to have a different cause as it occurs in complex environments and higher render distances and is probably VRAM related.
Not sure if already said before, but most lags and performance issues are a result of blindly relying on hyperthreading which slows the whole game down if not supported by the CPU (it’s is actually VERY common).
I think the blame lies solely on the new lighting engine added in 14w30a-c.
Two major engine updates occurred on this development cycle: threaded chunk loading and lighting engine changes to try to eliminate black spots.
First Great Job Leslie. Amazing work putting all this together
Instead of dark spot now I'm getting light spots, places in the world that are lit up for no apparent reason. I've seen this in several places now including caves.
ATTACHMENTS
2014-09-03_12.44.45
2014-09-03_12.44.52
Rollback Post to RevisionRollBack
Please actually read posts before responding, so you don't end up looking stewped.
The Meaning of Life, the Universe, and Everything.
Join Date:
3/4/2014
Posts:
57
Minecraft:
__tehface__
Member Details
after messing around with it, i have managed to get a framerate for around 700ish ( yea i know! ) and messed with the settings so there's no in game lag ... ( things moving really damm slow ) although when making a new world still takes ages to " make " but eh worth it
Overall I would say that my performance in 1.8 is about the same as 1.7.
However, I have noticed that in order for this to be the case I need to turn VBOs on. With VBOs enabled I get significantly less block lag and less screen image tearing. I might also try to update to java 8 soon as that seems to have worked for many people in helping to increase performance. I'm still hoping Mojang come out with a 1.8.1 to optimize the new rendering engine even more so that those who are currently having major trouble with the update (of whom it seems there are quite a few) will be able to play lag free.
Word on the grapevine is that the fps issue can be resolved by installing Java 8 (any version except update 20). However, Java 8 is incompatible with Forge for some reason, so you'll lose that option. I have no idea why that is. (edit: maybe it was just Forge that didn't like Java 8u20. I should probably figure that out.)
As far as what could be causing the stuttering, Java 8 is supposed to have a different and improved garbage collector. In Minecraft 1.8, all Vec3s and AABBs have had their instance pool removed and are now immutable types. It's possible that Java 7 is not respecting the immutable attribute and is causing Minecraft to hemorrhage orphaned records every GC.
Other folk are blaming the VBOs. I have no idea what that setting does that it wasn't doing before, so I can't really say whether this might be the case. Bunch a magic and hoopla is what it is.
I wonder if the poll's results are reliable, or if they're a consequence of selective bias. Just food for thought.
That being said, initially, I lost about 20-30 FPS after upgrading to 1.8. I went into the video settings and turned on VBOs (vortex buffer objects). My FPS is now back at a solid, steady 60, and the FPS fluctuations I was experiencing in 1.7.x are now nonexistent.
While FPS at a given time may be higher in 1.8 the frame time is overall much worse (frame time affects the perception of how smooth the game plays).
That's likely to vary from player to player, though. My overall framerate (if I uncap FPS) is about the same as it was in 1.7, if not a smidge higher. I'm not sure that, as a community, we have the tools to accurately gauge an overall FPS increase or decrease for more than a small sample of the overall Minecraft population.
Just gotta say that updating to Java 8 actually did help quite a bit for me. There's still some problems with slow chubk loading in creative mode, but if you're just playing survival it seems pretty fine. No block lag, and everything just feels faster and smoother than before. Maybe I'm just lucky, but it has helped a bit for me, and I just wanted to mention it :).
I'll definitely give it a try, i didn't even know java 8 was already available.
Anyway, my fps got terribly worse, i got a bunch of chunk errors on my main world and the game just crashes when i open a world/log in to a server with my 1.7 audio pack.
The Meaning of Life, the Universe, and Everything.
Join Date:
1/19/2013
Posts:
46
Minecraft:
Axandro
Xbox:
Denpaxandro
Member Details
Just because you don't have the same problem doesn't mean that others are not, nor does that mean you should just be like "your PC sucks mine can play 1.8 perfectly" even though not only people with normal computers are experiencing this problem, people with computers BUILT FOR PLAYING MINECRAFT are also experiencing this problem... So next time THINK before you say that someone's PC sucks just because 1.8 has this problem on their PC... just my opinion though.. you don't have to listen to it if you don't want to.
span>And about the things they added from mods: When mod X has cool feature Y, then people keep bugging Mojang with feature requests "Add feature Y to vanilla!!!", then when it's added, they complain that "feature Y has been stolen from mod X". You should be happy that at least they listen to the community
Most of the people who complain of these new additions to the game that are similar to the mods are the ones who are against these said additions.
There is no way that I should be getting bad fps but I am.
On single player it runs between 55 and 60 fps. on other server (not realms) it runs 55 to 60. Maybe there it has something to do with the world I uploaded.
For comparison, this is while running 1.6.4, which uses near 100% CPU all the time (split about 3:1 between the javaw and dwm processes, which presumably updates the display), but doesn't lag, so it appears that something is preventing 1.8 from efficiently utilizing the CPU:
Perhaps it is the extreme memory bandwidth used by 1.8, as seen by watching the memory usage, which rises at an extremely fast rate, several hundred MB per second (also mentioned in this thread), before rolling over and repeating the cycle; memory usage in 1.6.4 only increases by a few MB per second. 400 MHz DDR RAM should be able to sustain those rates though.
Most interesting is what happens when I turn Advanced OpenGL off in 1.6.4 (which was removed due to issues in 1.8, also causes occasional invisible chunk sections in 1.6.4 but Optifine fixes it):
This also drops average FPS by about half, but still entirely playable, around 40-50 FPS on Normal and Fast, with some lag when turning around in windowed mode, but the lag appears to have a different cause as it occurs in complex environments and higher render distances and is probably VRAM related.
The issue could also be this, mentioned in a bug report on performance issues:
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
I'm back
Amen
Jimmy followed "christopher hercules " post within that previously mentioned link. Jimmy is seeing a good bit of improvement from before. Thanks.
First Great Job Leslie. Amazing work putting all this together
Instead of dark spot now I'm getting light spots, places in the world that are lit up for no apparent reason. I've seen this in several places now including caves.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHowever, I have noticed that in order for this to be the case I need to turn VBOs on. With VBOs enabled I get significantly less block lag and less screen image tearing. I might also try to update to java 8 soon as that seems to have worked for many people in helping to increase performance. I'm still hoping Mojang come out with a 1.8.1 to optimize the new rendering engine even more so that those who are currently having major trouble with the update (of whom it seems there are quite a few) will be able to play lag free.
Which is then balanced by:
.
- The Cubic Chunks Mod is back! Be a part of it's rebirth and Development.
-- Robinton's Mods: [ Mirror ] for some of his Mods incl Cubic Chunks Mod, due to DropBox broken links.
- Dungeon Generator for the Open Cubic Chunks Mod
- QuickSAVE-QuickLOAD for the Open Cubic Chunks Mod
That being said, initially, I lost about 20-30 FPS after upgrading to 1.8. I went into the video settings and turned on VBOs (vortex buffer objects). My FPS is now back at a solid, steady 60, and the FPS fluctuations I was experiencing in 1.7.x are now nonexistent.
That's likely to vary from player to player, though. My overall framerate (if I uncap FPS) is about the same as it was in 1.7, if not a smidge higher. I'm not sure that, as a community, we have the tools to accurately gauge an overall FPS increase or decrease for more than a small sample of the overall Minecraft population.
I'll definitely give it a try, i didn't even know java 8 was already available.
Anyway, my fps got terribly worse, i got a bunch of chunk errors on my main world and the game just crashes when i open a world/log in to a server with my 1.7 audio pack.
I can't think of another signature yet.
Press F3, then look at the first line.
Most of the people who complain of these new additions to the game that are similar to the mods are the ones who are against these said additions.
That is not bad FPS. That is average FPS.
If you are planning to make a suggestion, please read this.
If you want to know more, you can read this.
For those who complain about post-Beta generation, you might want to see this.
█▄▄█ █▄█▄█ █▀▀ ▀▀█ █░░█ █░▀░█ █▀▀
▀░░▀ ░▀░▀░ ▀▀▀ ▀▀▀ ▀▀▀▀ ▀░░░▀ ▀▀▀