Re: Schema provider/CA lookup status

Hi

> We've debugged and profiled this extensively and the hashing is the
> culprit.
>
> http://sourceforge.net/mailarchive/forum.php?thread_id=12989125&forum_id=32048
>
> If you fix the hashing the performance equals that of schemas defined at
> module level. If you want to verify this, just change the hashing line
> to "hash = id(s)" (This is obviously not a proposed fix)
>
> > So, is VSS a viable option? Or should I try to repllicate what ATSENG is
> > doing?
>
> Let's just fix the hashing. Maybe we can just invalidate the cache when
> schema's are edited or hash the schema with it's modification date.


So what is a valid hash? And why exactly is this hash causing cache misses?
Is __dict__ not stable enough?

Martin

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Archetypes-devel mailing list
Archetypes-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/archetypes-devel