Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re: A distributed design challenge

by moritz (Cardinal)
on Jun 29, 2012 at 17:26 UTC ( #979155=note: print w/replies, xml ) Need Help??

in reply to A distributed design challenge

I don't have any experience with such systems, just a few naive ideas:

  • give every machine a local budget, and only talk to the central server when the local budget is exhausted. This shoudl reduce load and thus contention on the central server
  • give every machine a local budget, and have it obtain budgets from other peers when its own budget is exhausted. If it can't do that (or can't do it fast enough), don't approve the transaction
  • Make something home-grown, simple and very fast on the server side for querying and changing the available budget. You'll only need to support very few operations (query and decrease budgets), so something tailored specifically to that use case might well be faster than a generic solution like redis
  • keep statistics about how many of your bids were successful, and use these stastistics to allocate local budgets

Replies are listed 'Best First'.
Re^2: A distributed design challenge
by Ovid (Cardinal) on Jul 02, 2012 at 18:51 UTC

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://979155]
NodeReaper does the danse macabre

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (5)
As of 2018-04-25 11:05 GMT
Find Nodes?
    Voting Booth?