Quote from: Matt Corallo on June 14, 2012, 06:10:58 PM

Quote from: interlagos on June 14, 2012, 06:09:01 PM

SatoshiDice seems to be a great way for core devs to get a taste of what it's like to handle a volume like this when bitcoin network starts to scale up and think of the solutions in advance.

And what is the solution they came up with? Kill the volume maker!
Doesn't sound good to me...

Stop. Thats not what I am suggesting, nor is this something that is being extensively discussed, I started this thread to see what the community would say in response.
The goal is not to kill anyone or prevent them from using bitcoin for their use-case. Read the thread please.

Sorry, but that's the impression I got because you also called them stupid and braindead.

From the quote below it's seems they are also suffering from the same issue you mentioned,
if "use transactions in a more conservative way" means avoiding multisend.
They are a young service and hopefully they will work this out.

Quote from: fireduck on June 13, 2012, 05:59:24 AM

Quote from: titeuf_87 on June 12, 2012, 04:10:37 PM

I realize satoshidice is sometimes slow... but for the past few days I always had to wait at least five minutes before I even know if I won or not. Often times it's even longer.

Is this just me? Or that happens to others too?

Sorry, that was a database change I made. I make it use transactions in a more conservative way which ended up being a good bit slower so it was having trouble keeping up with people's bets. It should be much better now. I really need to track some metrics of bet to result time so that this sort of issue is more obvious to us.