Re: [Gems-users] Ruby_cycles varying in a wide range

["Dan Gibson" <degibson@xxxxxxxx>]

Looking at Notary, there seems to be more variance at coarser granularities of conflict detection (e.g. smaller signatures). 

Its good to have your observation of determinism with 2.2.19. This is something we're looking into internally -- so far it seems to be limited to 3.x+.

Our usual strategy is to automatically set random_seed from time(NULL) or some other source, then run as many runs as we need to achieve believable error bars. I don't use the STAMP workloads myself, so I cannot tell you how many runs that might actually be. 

Regards,
Dan

On Thu, Nov 27, 2008 at 9:08 AM, Ricardo Quislant del Barrio <quislant@xxxxxxxxx> wrote:

Hi Dan, thanks for your answer.
I've just simulated Labyrinth with random_seed set and every simulation
returned the same number of ruby cycles. So Simics seems to be
deterministic (I'm using 2.2.19).
May be it will be a problem with H3 filters or Timestamp conflict
resolution policy, I'll try with Hybrid.
Just a last question: What do you use to do? Do you change random_seed
manually or do you
set it to None?

Thanks Dan,

Ricardo

_______________________________________________
Gems-users mailing list

Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.

-- 
http://www.cs.wisc.edu/~gibson [esc]:wq!