On 10/8/06, Daniel <[EMAIL PROTECTED]> wrote: > I'll try a few earlier dates when I get a chance, and then I'll let > you know how they perform.
cool > >>> shelve.Pickler.__module__ > 'cPickle' > >>> shelve.StringIO.__module__ > 'cStringIO' mmm, same as me. > Interestingly enough, I grabbed that tool and ran my user database > through it. I get *one* user listed with his username, password and > subscription status. The file is about 750KB, so I'm pretty sure > there's more data in there (not to mention my being able to look > through it for occurrences of my username and such). So do you think > ti sounds like the file is corrupt? Maybe I should just trash it and > start it over. Has the format of the file changed any since the last > release? I doubt the file is corrupt, just that the 'shelve'/'pickle' formats are probably not great. You probably find that they don't zero memory, and use lazy storage, etc. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Sun Oct 8 17:09:18 2006 From: [EMAIL PROTECTED] (Brian Safford) Date: Sun Oct 8 17:10:08 2006 Subject: [py-transports] PyYIMt avatars In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Yes indeed ... and will do so as soon as I receive ( and test ) them from my friend who has been pretty busy lately :-) On Sun, 2006-10-08 at 16:58 +0200, Norman Rasmussen wrote: > On 10/8/06, Brian Safford <[EMAIL PROTECTED]> wrote: > > Please keep large implementations in mind while engineering this ... > > once I can get PyYIMt patched to work with Jabber XCP, I have about > > 12,000 users (3,000 concurrent) to throw at it ... > > Yea, I'd prefer to keep the data file small to make the accesses > faster. (Less data means faster right?) Avatar access is relatively > seldom, so moving the data out of 'primary' database can only help > there. > > btw: I think you promised to send the XCP patches in this direction :-P >
