- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: allocation memory problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2011 06:19 AM
тАО05-03-2011 06:19 AM
allocation memory problem
I suspect that my 64 bit application when crash when alloc more than 4 Gb of memory.
I need a script that can be alloc more than 4 Gb
8 Gb is perfect .
the kernel parameter and ulimit are ok.
ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194300
stack(kbytes) 392192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 4096
- Tags:
- ulimit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2011 06:30 AM
тАО05-03-2011 06:30 AM
Re: allocation memory problem
Why do you need a script if your application just does fine running out of memory?
What error (the 'errno' and the message does your application report? I assume that it is a well-behaved one that does.
What does your swap space look like when your application dies?
For what is 'maxdsiz_64' set?
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2011 07:19 AM
тАО05-03-2011 07:19 AM
Re: allocation memory problem
Please do:
file nameofexe
It could be you have a 32bit app good sir and even if you re-quadrant, your 32 bit app will not be able to use no more than 3.9GB of memory (total of data, text and stack).
Cheers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2011 12:47 AM
тАО05-04-2011 12:47 AM
Re: allocation memory problem
maxdsiz_64bit 4396972765184 4396972765184 Immed
maxrsessiz 8388608 Default
maxrsessiz_64bit 8388608 Default
maxssiz 401604608 401604608 Immed
maxssiz_64bit 2147483648 2147483648 Immed
pa_maxssiz_32bit 83648512 Default
pa_maxssiz_64bit 536870912 Default
shmmax 68719476736 68719476736 Immed
shmmni 2896 2896 Immed
shmseg 1024 1024 Immed
This is my kernel parameter ...
My application is :
file /sas_SNA/CLA/SAS_SW/SASFoundation/9.2/sasexe/sas
/sas_SNA/CLA/SAS_SW/SASFoundation/9.2/sasexe/sas: ELF-64 executable object file - IA64
I suppose that this script call a java that failed over 4Gb.
how can test start of java with more of 4 Gb ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2011 11:49 AM
тАО05-04-2011 11:49 AM
Re: allocation memory problem
Good luck, only if you have a 64 bit shell.
>the kernel parameter and ulimit are ok.
ulimit is useless for setting sizes for 64 bit apps, what are the kernel parms:
kctune | grep "max.*siz"
Note: maxssiz 401604608
This may be too big for a 32 bit app. Every byte in maxssiz takes away a byte in your heap.
>I suppose that this script call a java that failed over 4Gb.
No scripts here, only executables.
>how can test start of java with more of 4 Gb?
You have to tell java to use a 64 bit version: -d64