Jonas Borgström wrote: > ... Four consecutive > "/report/1" requests gives the following output: > > before render(): 51888 kB > after render(): 209456 kB > before render(): 208936 kB > after render(): 221792 kB > before render(): 222040 kB > after render(): 222128 kB > before render(): 222128 kB > after render(): 222128 kB >
> And since python 2.5.2 never seems to return "free" and garbage > collected memory back to the operating system this memory is bound to > this particular process until it is restarted. > No, Python 2.5.2 is able to do that. If instead of looking only at before/after memory usage, you monitor the memory used while processing the request, you'll see that there's a peak usage (which I estimate at around 350MB, given your numbers above are close to mine). So that's 130MB returned to the system. That's not enough I agree, but it's probably not because Python can't give back memory to the system, rather because there are some leaks which prevent the memory to be freed. > This is bad news for people running multiple long running processes > since after a while all processes will have allocated enough ram for the > most expensive page. > > So far I've been unable to find a way to minimize the memory usage of > genshi's serialization step. But unless we find any way to do that I'm > afraid we might have to consider paging or some other technique to avoid > these expensive pages. > There is a good patch for report paging (#6127 / #216), so I'll move that up in the queue. But on the other hand, there might well be a report specific issue (or a Genshi issue uncovered by the report_view.html template), as I also have very big numbers (memory and time) for the reports in my tests. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
