Question

我们的产物目前为32比1.6英亩。我们重新使用伯克利分行,它消耗了4个GB地址中的大约2.5个GB RAM。这使我们想到大约750兆赫用于其地址的甲基溴记忆。

We re currently hitting OutOfMemory issues with the current setup. It would be nice to increase our JVM heap size to 1.5 GB while still retaining Berkeley DB s 2.5 GB space. Is there any way to access more than 4 GB RAM/heap in a 32-bit JVM ? I ve considering the following solutions
1) use a JVM which does better GC -- this will give me marginal results -- I could get about 50-100 MB working memory
2) something like memcached or "out of process ehcache " -- this can get me as much as the hardware allows with the overhead of IPC/serialization.

是否有其他办法增加应用记忆?

解决办法应涉及太阳系10。

* 。 UPDATE :由于现在使用本土共享图书馆,我们不得不转而使用64比方位的JV,尽管本组织是64比方()。

感谢您,

Answer 1

是否有其他办法增加应用记忆?

Split single application in several processes with non-shared memory (not a threads; but processes). First process can run DB and second can run other part of the project. You can use RMI or shared memory or sockets to communicate between processes.
Lower memory, reserved for OS. E.g. on x86-32 PAE allows OS to reserve a smaller than 1 GB of 4 GB virtual address space. (e.g "4GB / 4Gb split", supported on Oracle Linux)
Put some data to the disk. The disk can be a RAM-disk to better speed; or it can be real disk and OS will speed up access to files using "page cache".

而且,每个实际的SPARC(不是古老的超级住房或贫穷住房)都是64倍。因此,转而使用64比方位的顾问很容易。我不知道太阳系,但在中枢轴上,在64位仲裁员中,有32项申请。而64位仲裁员将允许你管理64比方位证书。

UPDATE: There are ramdisks in Solaris http://wikis.sun.com/display/BigAdmin/Talking+about+RAM+disks+in+the+Solaris+OS and I think you should try them for storing database (or temporary files of DB). There will be no extra serialization/IPC like in case (1); only extra read/write or mmap/munmap. But Ramdisk is order faster than SSD and 3-4 orders faster than HDD.

Answer 2

32个轨道方案无法处理4个以上的记忆地址。他们只是没有足够东西来代表更多的记忆。

2^32 = 4 294 967 296

您的最好用心是提升到64倍的JRE。

Answer 3

I suggest you run your 32-bit shared native libraries in a 32-bit JVM and run everything else in a 64-bit JVM. You can have the 64-bit JVM call the 32-bit JVM to do whatever it does. I assume the bulk of your data/memory requirement can be moved to a 64-bit JVM.

友情链接