Jdeveloper being slow when shifting the application in windows. Reason being the windows swapping the jdeveloper memory even when large amount of physical memory is available.Application has a working set size. The default value is much too small for big Java applications like Eclipse. Hence, windows does a swapping. To prevent this, one thing that can be done is to increase the minimum water mark of this working set size. Then, there is another problem that when the user memory is less than the minimum working set size, windows will think that the application is not used and will do swapping again. Using VirtualLock() will prevent this and force Windows to keep Eclipse in memory.
Got this information from the blog : http://www.orablogs.com/gdavison/archives/001659.html
FAQ on this plugin also provides a clear information : http://suif.stanford.edu/pub/keepresident/faq.html
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment