Re: Lookup caching

2006-12-12 Thread Andrea Griffini
MRAB wrote: ... > What are you using for the timestamp? Are you calling a function to > read a timer? For timestamp I used a static variable; to update the timestamp for a dictionary I used d->timestamp = ++global_dict_timestamp; I'm using a single counter for all dicts so that when doi

Re: Lookup caching

2006-12-12 Thread MRAB
Andrea Griffini wrote: > Gabriel Genellina wrote: > > At Saturday 9/12/2006 23:04, Andrea Griffini wrote: > > > >> I implemented that crazy idea and seems working... in its > >> current hacked state can still pass the test suite (exluding > > > > What crazy idea? And what is this supposed to do? >

Re: Lookup caching

2006-12-11 Thread Andrea Griffini
Gabriel Genellina wrote: > At Saturday 9/12/2006 23:04, Andrea Griffini wrote: > >> I implemented that crazy idea and seems working... in its >> current hacked state can still pass the test suite (exluding > > What crazy idea? And what is this supposed to do? > The idea is to avoid looking up co

Re: Lookup caching

2006-12-11 Thread Gabriel Genellina
At Saturday 9/12/2006 23:04, Andrea Griffini wrote: I implemented that crazy idea and seems working... in its current hacked state can still pass the test suite (exluding What crazy idea? And what is this supposed to do? -- Gabriel Genellina Softlab SRL ___

Lookup caching

2006-12-09 Thread Andrea Griffini
Hello, I implemented that crazy idea and seems working... in its current hacked state can still pass the test suite (exluding the tests that don't like self generated output on stdout from python) and the stats after the quicktest are IMO impressing: LOAD_GLOBAL = 13666473 globals miss = 58988 bu