There was a discussion about this in the Linux community a few years ago and
some kernel developer claimed to having good results from designating a
RAM-drive to be swap. Maybe it's a good middle road between keeping the
functionality that now depends on swap and not using disk...
BR,
John
On
if the RAM drive itself needed to swap, we might not need the large
hadron collider. sounds like black hole territory :)
On Jan 2, 8:10 pm, John Nilsson j...@milsson.nu wrote:
There was a discussion about this in the Linux community a few years ago and
some kernel developer claimed to having
yes, I meant heap size - -Xmx is limiting the heap size but not the
mmapped memory - to me it becomes a discussion about how many objects
a java app can have at the same time and at what count of objects you
might want to reconsider your design approach as well as do we really
need to store
Actually it can work nicely. I use TMPFS for my dev work, it
automatically uses available/specified amount of RAM but starts to use
swap if required. By my experience, that approach speeds up Ant and
Maven builds by order of magnitudes - makes NetBeans fly.
/Casper
On Jan 2, 11:52 am,
Not too long ago, I wrote a simple BeanShell script that loaded large files in
memory, did some transformations on them and dumped results as output files.
After bumping into the heap limit a few times, I decided to give myself a good
way of monitoring memory usage via standard Runtime API.
Yeah, I didn't meant to suggest it wouldn't work. I'm just keeping up
my quota of non-serious posts. :)
On Jan 3, 1:15 am, Casper Bang casper.b...@gmail.com wrote:
Actually it can work nicely.
--~--~-~--~~~---~--~~
You received this message because you are
