Search the Community

Showing results for tags 'heap size'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Official Buildings
    • GM Hall
    • City Hall
    • Website News
    • Public Test Board
  • Back Streets
    • Town Square
    • Community Assistance
    • Village Recruitment Center
    • Suggestions & Ideas
    • The Creative Commons
    • Wood Scraps
  • Northern Freedom Isles
    • Harmony
    • Melody
    • Cadence
    • Northern Freedom Isles Market
  • Southern Freedom Isles
    • Celebration
    • Deliverance
    • Exodus
    • Independence
    • Pristine
    • Release
    • Xanadu
    • Southern Freedom Isles Market
  • Maintenance Buildings
    • Technical Issues
    • Server Bugs
    • Client Bugs
    • Model and Sound Bugs
    • Other Bugs and Issues
    • Wurmpedia / Wiki Maintenance
  • Wurm Unlimited
    • Unlimited Discussion
    • Server Listings & Advertisement
    • Unlimited Modding
    • Technical Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Gmail


Facebook


Twitter


Discord


Skype


Instagram


Snapchat


LinkedIn


Reddit


YouTube


Yahoo


MSN


Website URL


Location


Interests


Chaos


Independence


Deliverance


Exodus


Celebration


Xanadu


Release


Pristine


Epic


Acc1


Acc2


Acc3

Found 1 result

  1. The last while I had some serious problem with CPU load spikes and lockups in Wurm: http://forum.wurmonl...l__+cpu +spikes I found some stuff to improve things on my end, but there is one issue with Wurm itself that I wanted to bring to attention: The Wurm client jnlp file is limiting Java heap size to 800MB. This is probably an older value that has never been updated to current requirements, like multistory. When the local area gets cluttered, the heap is simply not big enough to hold all the data and the Java Garbage collection is running into a wall, jumping into full mode, which locks up the program until it's done. The problem could easily be alleviated by increasing heap size, but unfortunattely the jnlp <max-heap-size> parameter seems to take precedence over the ecternal javaws -Xmx option. Can't manually edit the jnlp file either, because there is a signature check. The incremental Garbage Collection option -Xincgc seems to work in preventing the lockups though. However a larger heap would probably improve performance. Edit: you can't have the heap size in the jnlp set too high in case of older machines though. Best would be a setting in the launcher that would start the game with a custom heap size. That way the user can adjust to his system. You could also use an automatic option by default that scales to maybe 50% system ram.