This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

Paging and its relation to Heap and Garbage collection in Websphere  RSS feed

 
Ranch Hand
Posts: 178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've encountered a lot of out of memory problems in the past dealing with Websphere Application server. Most have been solved by proper tuning of Websphere settings (heap size, thread pools etc) or optimization of the applications deployed in it. When finding solutions for those problems, one thing I always read or hear is the suggestion of changing the "paging" settings. Never really understood what its for. What does it have to do with garbage collection and heap settings in Websphere?

Can someone explain this to me in simplest terms?

Is it difficult to tune this? is it more on tuning the server OS settings and not websphere?
 
Bartender
Posts: 19731
92
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As far as I know, there are no commercial JVMs that actively involve themselves in interacting with virtual memory paging, although at least one experiment has apparently been done.

It's generally considered to be a good idea to have sufficient real memory to hold the entire VM without any OS-level paging at all.

The nightmare scenario comes when the objects being handled in virtual memory (the "working set") exceed available free page slots, forcing a high page rate in order to do things like traverse a hypothetical garbage-collection list, and in particular when the working set is being randomly accessed. That's because it can take thousands of times longer to page out an unused page and page a new page into the vacated slot than to do a simple read from RAM, and if you're doing stuff that sends the page in and out a lot, it will slow your app down to a crawl and beat the disk drive silly.

Someone once "proved" that OS/2 was slower than a Commodore-64 by doing just that, in fact.

Memory is cheap these days. In fact, it costs a lot less to install a few extra sticks in a server than it does to pay a highly-trained expert to optimize paging.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!