View Single Post
Old 12-16-2010, 03:23 PM   #26
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,450
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
I can't think of anything that could cause more paging in newer releases. That said, in fixing memory leaks I have changed the way object references are stored/garbage collected in various parts of the calibre code and that might be causing this, though I don't know enough about the internals of python's garbage collection/windows memory management to speak with any confidence.

As long as the speed recovers after the initial add of a format, I'm not going to spend more time on this. I will note that I don't notice any post idling slowdown on my linux machine but then that has 6 GB of RAM and linux never pages anything unless it really has to.
kovidgoyal is offline   Reply With Quote