Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5333

Closed (moved)
(moved)
Open
Created Mar 08, 2012 by Roger Dingledine@arma

Make simulator authors aware of "clients have different connectivity" wishlist item

In #4487 (moved) I want to understand how n23 behaves when the client's first hop is flaky.

But all the Experimentor and Shadow graphs I've seen so far look like the clients all have the same connectivity, and the graphs are averages of client results.

I guess we could run the experiments where every client has a flaky first hop. But that wouldn't capture the case where most clients are hammering the network, and our poor client can't hammer the network because his connectivity isn't good enough.

Can the two simulators capture different client bandwidth/connectivity properties? How hard would that be to add?

(I ask because I hope to ask for simulation results early next week once we've resolved #4488 (moved).)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking