62,623
社区成员
发帖
与我相关
我的任务
分享请发表友善的回复…
发表回复
heifei 2007-12-26
- 打赏
- 举报
我这里也有linux６４位的环境，只是不知道windows 64位下jvm内存分配上限是什么情况？
Gump09 2007-12-25
- 打赏
- 举报
8G的应用是有的。不过关键不是memory size而是gc的效率。
64bit可用的heap size 是相当大的几乎不用考虑。
楼主可以看一下对websphere的描述。
For IBM on the 32-bit Windows platform, the maximum heap size we could use was 1640 megabytes RAM (the theoretical limit is 2048 megabytes or ~2 gigabytes, however we found the default install of WebSphere will not start on 32-bit Windows with a heap size greater than 1640 megabytes, possibly due to the fact the JVM requests a contiguous block of memory for the heap, and Windows 32-bit doles out up 1,640 megabytes of contiguous memory per process). On Linux, we were able to configure the 32-bit WebSphere heap size to 2,300 megabytes of RAM, which represents more RAM available for cache entries on Linux vs. Windows for 32-bit WebSphere. For 64-bit WebSphere on Windows, we were able to run with a heap size of 14,500 megabytes without incurring OS swapping. For 64-bit WebSphere on Linux, we were able to also run with a heap size of 14,500 megabytes without incurring OS swapping (see the heap size setting discussion for a more detailed explanation). For WebSphere, we found the maximum number of entries allowed in the cache (within a margin of roughly 500 entries) via trial and error -- simply by running with an estimate of 500K per entry up to available heap size, then running the test with a max cache entry value until we found the point at which WebSphere would not crash/heap dump. For 32-bit Windows/ WebSphere, this number was 2500 entries. For 32-bit WebSphere on Linux this was 3000 entries. For 64-bit WebSphere the numbers were 27,000 allowable cache entries on both Windows 64-bit and Linux 64-bit, respectively given our matching configured Java heap sizes on these platforms.
64bit可用的heap size 是相当大的几乎不用考虑。
楼主可以看一下对websphere的描述。
For IBM on the 32-bit Windows platform, the maximum heap size we could use was 1640 megabytes RAM (the theoretical limit is 2048 megabytes or ~2 gigabytes, however we found the default install of WebSphere will not start on 32-bit Windows with a heap size greater than 1640 megabytes, possibly due to the fact the JVM requests a contiguous block of memory for the heap, and Windows 32-bit doles out up 1,640 megabytes of contiguous memory per process). On Linux, we were able to configure the 32-bit WebSphere heap size to 2,300 megabytes of RAM, which represents more RAM available for cache entries on Linux vs. Windows for 32-bit WebSphere. For 64-bit WebSphere on Windows, we were able to run with a heap size of 14,500 megabytes without incurring OS swapping. For 64-bit WebSphere on Linux, we were able to also run with a heap size of 14,500 megabytes without incurring OS swapping (see the heap size setting discussion for a more detailed explanation). For WebSphere, we found the maximum number of entries allowed in the cache (within a margin of roughly 500 entries) via trial and error -- simply by running with an estimate of 500K per entry up to available heap size, then running the test with a max cache entry value until we found the point at which WebSphere would not crash/heap dump. For 32-bit Windows/ WebSphere, this number was 2500 entries. For 32-bit WebSphere on Linux this was 3000 entries. For 64-bit WebSphere the numbers were 27,000 allowable cache entries on both Windows 64-bit and Linux 64-bit, respectively given our matching configured Java heap sizes on these platforms.
老紫竹 2007-12-25
- 打赏
- 举报
请参考这篇文章
http://www.w3china.org/blog/more.asp?name=hongrui&id=23973
声明，我没测试过，不敢确认，2G我可以确认！
http://www.w3china.org/blog/more.asp?name=hongrui&id=23973
声明，我没测试过，不敢确认，2G我可以确认！
victoryzll 2007-12-25
- 打赏
- 举报
看看楼下怎么说的
记得好象不能到8G SUN的
记得好象不能到8G SUN的
victoryzll 2007-12-25
- 打赏
- 举报
好象只能到2G吧
SUN的SOLARIS可以到8G？
SUN的SOLARIS可以到8G？
victoryzll 2007-12-25
- 打赏
- 举报
圣诞快乐
victoryzll 2007-12-25
- 打赏
- 举报
枪到沙发了
老紫竹 2007-12-25
- 打赏
- 举报
到处问哦！
最大使用2G，不过有消息，Sun 的Solaris 可以到8G？ 我没用过，不确定。
最大使用2G，不过有消息，Sun 的Solaris 可以到8G？ 我没用过，不确定。
heifei 2007-12-25
- 打赏
- 举报
我这里也有linux６４位的环境，只是不知道windows 64位是什么情况
shaot399 2007-12-25
- 打赏
- 举报
在jdk1.5以后，在64位操作系统上，jdk已经没有最大内存的限制，经过测试，当内存用的比较大的时候，当用到交换分区的时候（linux系统），虚拟机会进行内存回收，此时机器压力是比较大的，整个机器基本上是不再响应请求
