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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|