"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > In our case, the issue is this: we load a ton of info at server > restart, from the database. Some of it gets processed a bit based on > configuration files and so forth. If this were done in my own C > server, I'd do all of that and set up the (read-only) runtime data > structures prior to forking. That would mean that: > a) The processing time would be lower since you're just doing the pre- > processing once; and > b) The memory footprint could be lower if large data structures were > created prior to fork; they'd be in shared copy-on-write pages.
If you completely control the server, write an apache module that dumps this data into a file on startup, then mmap it into your Python app. -- http://mail.python.org/mailman/listinfo/python-list