On 14/07/2006, at 6:53 PM, David E Freitas wrote: > On 7/14/06, James Bunton <[EMAIL PROTECTED]> wrote: >> On 04/07/2006, at 2:02 AM, Lucas Nussbaum wrote: >> > Hi, >> > >> > We are running pymsnt on a quite large server, and it uses much >> more >> > CPU/ram than we would prefer it to use. It would really be great >> > if, in >> > the future, you could add a way to disable some of the non-core >> > features >> > (avatars, file transfers, ...). >> > >> > Do you have some plans of adding something like that yourself ? We >> > might >> > start working on a patch if you don't. >> > >> > Thank you, >> >> I don't plan on making avatars optional. I'd rather make them more >> efficient :) >> >> I'd like for the transport to offer a certain set of minimal features >> on all servers. Avatars are very important to some people, so they're >> included in that. >> >> I do plan on making the transport as a whole more efficient though, >> both memory & cpu wise. >> >> --- >> >> James >> > > Thanks James, > > Why not have avatars as an optional default on? No pressure though. > It's just that on big servers, having images transferred when they > aren't being used can be quite a waste of bandwidth. > > So, what are the plans to optimize memory/cpu? > > Any threading plans? > > > Thanks,
Having avatars as an option would complicate the code. I don't consider the bandwidth used to be too much. They are cached and generally retrieved from disk. There is an option <getAllAvatars/> which you can comment out so that avatars will only be retrieved for contacts that users have a conversation with. I plan to run over the code with a profiler again to optimise/fix any hotspots. I also plan to make the transport run in psyco. I plan to have all data read/written to disk in a seperate thread, to keep the main event handling thread clear. As far as memory goes, there are some objects that aren't being freed properly under all circumstances, I have some restructuring planned to fix that. --- James
