Hey Goetz, 2008/11/24 Goetz Babin-Ebell <[EMAIL PROTECTED]>: >> The way you phrase your question suggests you saw a big jump in memory >> usage with the latest release? > > With 2.1.5 it was a problem (20MB), but not that burning...
I think I have found a reason for this behaviour: threads were allocated but not used when using the built-in httpd controller. I have fixed this in CVS. >> What do you mean by using 36MB of RAM? Is this total mapped memory? > VmData(36532K) + VmStack(84K) These (I assume you read this from the /proc filesystem) are memory sizes that are mapped, but do not reflect what is actually used. To see what is used, you could use a memory profiling tool, such as valgrind's massif With a default Wt debug build (including SSL), and the default of 10 threads (not sure if that matters for heap usage), the actual heap memory used after starting hello world is 300,568 bytes. The main users indicated by massif are boost::asio (33%), SSL initialization (16%) and boost::regex used in CgiParser (which you can disable on linux with a compile time option HAVE_GNU_REGEX). >> You should probably also differentiate between shared (rx) en >> non-shared (rw) memory segments? > Only stack and heap... That is okay. But, those are mapped memory, not actually used. Mapped memory does not consume memory untill it is actually used (i.e. swapped in). Regards, koen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
