On Fri, Jun 12, 2009 at 4:15 AM, Jurie-Jan Botha <[email protected]>wrote:
> > It feels ridiculous to me but we've got a filter tag that's making a > mess of our cache. > > Here's the deal: > * We cache lots of stuff on our site using low level cache api and > cmemcache. > * We've got a float field on a model that we cache. > * When we use this float field in a template it works fine. > > But! When we use the 'floatformat' filter tag we get a bunch of the > following message in our server output/log and our cache is broken > (carries on like it's empty): > mcm_get_line():1547: memcache(4) protocol error: no \r before \n > > I really don't see how using the filter tag could influence our cache, > but it's really all that stops the error from appearing. > > Versions: > cmemcache - 0.95 > memcache - 1.2.8 > libmemcache - 1.4.0.rc2-1 > We had this issue for some time and am actually really interested in the fact you seem to have been able to dig deeper than us by pointing to the floatfilter (even though I don't think we use this in our code base). >From all of my searching for this issue, it seems to be a problem with .95 cmemcache, Downgrading seemed to have fixed the problem. We also switched over to the python memcache library because we were able to review the code and see it in all its simplicity and things worked fine as well. I would love to hear about fixes because the speed up in queries between the 2 modules is 1.5 on our code base, but it wasn't worth the error logs and my paranoia wondering what the problem has been. Let me know if you get anywhere else with this, Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
