Re: [tor-dev] Prop259 simulator and results

Reinaldo Junior writes: > - number of guards we tried until the first successful circuit > - time until the first successful circuit is built > > A successful circuit is one which we succeeded to find a guard using the > algorithm AND we succeeded to connect to it. > >

Re: [tor-dev] Prop259 simulator and results

On Wed, Feb 17, 2016 at 2:16 PM, Reinaldo Junior wrote: > [...] > > By default, we recreate the client (OP) every 2 minutes (which makes it > bootstrap, and so on). We can configure to simulate a long lived client, > and in this case it fetches a new consensus every

Re: [tor-dev] Prop259 simulator and results

imentinOn Wed, Feb 17, 2016 at 8:29 AM, George Kadianakis < desnac...@riseup.net> wrote: > Hello there, > > I'm not sure what kind of statistics we get out of the current guard > simulator. > The simulation creates a network with 1000 relays (all guards) with 96% of reliability, and using

[tor-dev] Prop259 simulator and results

Hello there, I'm not sure what kind of statistics we get out of the current guard simulator. In general, we are interested in security and performance. For security we are trying to minimize our exposure to network. For performance, we want to minimize our downtime when our current guard becomes

Re: [tor-dev] Next version of the algorithm

Hey, > > Returning to this for a bit. I think it would be good to decide whether we > should keep the unreachable status of guards on permannet disk state or > not. The > very latest prop259 basically forgets the unreachable guard status as soon as > the algorithm terminates. I wonder if we