why all the lag with monster?

[Kahless61]

Just an FYI, number of cores doesn't mean a heck of a lot with stuff that is mostly single-threaded. Open your process manager for whatever OS you're running minecraft on and check out the load on each core next time you play. You'll probably be upset.

Figured I'd share this. The last time I ran Monster. What you see here is me finishing up and quitting to the menu screen (hence the flatline). As you can see, it actually uses all 4 cores, albeit the last 2 cores don't get used all too much, and most of the work is on the first core.

Moral of the story is, extra cores help, to a decent extent, but they're certainly not a magic bullet.

Also, for those of you who said only one core is used, you're clearly wrong. As long as you have your JVM arguments set properly, FTB will use all 4 cores.

 

[PhishTV]

just to update if any have the same issue I was........ I disabled mariculture mod and there is no more lag on server to bad I really wanted the coral reefs and boat travel works fine now

I am curious as to how much of your RAM was being used. I have a 2gb dedicated server for 2 people. In unleashed this RAM used to be barely used however when us 2 are online in Monster the RAM sits around 1.8gb to 1.9gb and thats with no machines built.

 

[twisto51]

That graph is for the system, not for a given process. Your system is making use of all 4 cores, doesn't mean the JVM containing minecraft is using all 4 cores.

Of particular interest are the spikes of CPU1 approaching 100% while the other 3 cores aren't doing significantly more than they do while at idle. The majority of the load is probably in a single thread at that point. If an individual core isn't up to keeping that going you're going to see a performance hit, whether you have 1 core or 100 cores. More cores isn't a magic bullet, multi-threaded code isn't easy.

There is a good article here that isn't too out of date. http://www.sk89q.com/2013/03/improving-your-minecraft-servers-performance/

 

[DriftinFool]

I play on single player. I have an I5 760 oc'd to 3.66 ghz. 8 gigs DDR3 @1600 mghz. Sata 3 connection to WD black 1TB drive. Graphics are 560 TI superclocked. My FPS stays around 60 because I use vsync. I am using the JVM arguments with the recommended allocated RAM. I have tried it with more and less RAM and neither made a difference. With the monster pack, I get lag spikes every so often no matter where I am, what I am doing, or if machines are running or not. I have mariculture disabled. After watching my FPS go from 59 to 28 by turning on one Mariculture water turbine and seeing other issues with it, i got rid of it. I still have these lag spikes while maintaining about 60 FPS. I have also generated the world all around me by flying in creative so there is no world gen causing it. I am also not running special mobs. I have never had an issue with any other mod pack.

It sure would be nice to figure out what is causing it. Misplacing blocks and destroying things I don't want to break because of a lag spike is annoying. It is especially annoying on a new world with nothing that should be causing it.

 

[Kahless61]

That graph is for the system, not for a given process. Your system is making use of all 4 cores, doesn't mean the JVM containing minecraft is using all 4 cores.

Of particular interest are the spikes of CPU1 approaching 100% while the other 3 cores aren't doing significantly more than they do while at idle. The majority of the load is probably in a single thread at that point. If an individual core isn't up to keeping that going you're going to see a performance hit, whether you have 1 core or 100 cores. More cores isn't a magic bullet, multi-threaded code isn't easy.

There is a good article here that isn't too out of date. http://www.sk89q.com/2013/03/improving-your-minecraft-servers-performance/

You're correct, but the flatline for the last 30 seconds is a pretty steady indicator of what the system was doing besides the JVM while I was playing. That is to say, a flat line at a low percentage. The point of the graph is really to demonstrate that FTB does indeed use all 4 cores, albeit not evenly - preferring the first core.

 

[twisto51]

You're correct, but the flatline for the last 30 seconds is a pretty steady indicator of what the system was doing besides the JVM while I was playing. That is to say, a flat line at a low percentage. The point of the graph is really to demonstrate that FTB does indeed use all 4 cores, albeit not evenly - preferring the first core.

And like I said before you're showing the usage for the entire system, not just FTB or more specifically the JVM that is running Minecraft. Your other cores could---and probably are---be going up simply because the system is using them for the I/O Minecraft is requesting. Come back with output for the specific process if you want to prove that Minecraft is using 4 cores. I seriously doubt you'll find that the case. Most likely it will be two, one large and one tiny at any given point in time.

 

[Bigglesworth]

Figured I'd share this. The last time I ran Monster. What you see here is me finishing up and quitting to the menu screen (hence the flatline). As you can see, it actually uses all 4 cores, albeit the last 2 cores don't get used all too much, and most of the work is on the first core.

Moral of the story is, extra cores help, to a decent extent, but they're certainly not a magic bullet.

Also, for those of you who said only one core is used, you're clearly wrong. As long as you have your JVM arguments set properly, FTB will use all 4 cores.

Sigh.

People that dont understand how things work should really stop themselves from making a 60 sec observation and concluding anything they please.

It isn't using 4 cores at the same time. It is uses 4 cores one at a time to spread heat. This is an OS level technique to keep one core from heating up disproportionately. MC doesn't use more than one core at one time. This isnt up for debate.

 

[extrastanding]

If you tweak the java arguments, you can get it to run garbage collection concurrently to put some load on a second core. That's probably the best you can do until someone gets tick threading working.