Carlo Sogono wrote: > We have 9GB of physical memory. At the moment, my application has to be > able to comfortably handle 4GB of memory handled by just *one* process.
I hope you have a 64 bit machine and you're talking about a 64 bit process. If you are trying to do this in a 32 bit process then you will be in trouble. A 32 bit process can only access 4Gig of memory and about 1Gig of that is needed for the kernel. > Our application will be mallocing and freeing simultaneously, but I am > trying to simulate our worst case scenario, wherein the process will > have to keep 4GB of data (160 byte chunks) in memory. Ok, you probably aren't running into memory fragmentation problems. > The application we're building is a relatively simple server / > application gateway for a telco. It just has to be able to handle a > large amount of data in memory. I am 101% sure my coding's logic is not > flawed, as it is a very simple application for now... If you are using a 32 bit process, you may want to consider splitting you app into separate processes now before you get too much further into your development process. Have you tried dstat yet? Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo +-----------------------------------------------------------+ "The phrase "object-oriented" means a lot of things. Half are obvious, and the other half are mistakes." -- Paul Graham _______________________________________________ coders mailing list [email protected] http://lists.slug.org.au/listinfo/coders
