Topic: Wall Observer - MtGoxUSD wall movement tracker - page 47. (Read 1811564 times)
ok, someone is "boxing" the price with large walls these past 1-2 hours, and now he pushed it to 90... what's the deal?
Meanwhile, the Gox verification queue keeps on growing. Now at 28,000+.
http://www.reddit.com/r/Bitcoin/comments/1ca5e4/mtgox_verification_times/c9eio88
http://www.reddit.com/r/Bitcoin/comments/1ca5e4/mtgox_verification_times/c9eio88
I'm still 20680 in queue... I should have verified my account long ago, but when I first registered, there was no verification process lol
I just saw it on CNN money as well earlier today.It does seem the popularity is getting on the major financial news stations in the US.
Link?
I just saw it on CNN money as well earlier today.It does seem the popularity is getting on the major financial news stations in the US.
Bid wall slipping, minute or so lag.
Bounce off $87 again?
Bounce off $87 again?
Meanwhile, the Gox verification queue keeps on growing. Now at 28,000+.
http://www.reddit.com/r/Bitcoin/comments/1ca5e4/mtgox_verification_times/c9eio88
http://www.reddit.com/r/Bitcoin/comments/1ca5e4/mtgox_verification_times/c9eio88
Hold on to your coins!
In a few years you'll be very sorry you sold them for $100-$200.
Once the FUD and manipulation clears and the coins are in the "right" hands, the price will skyrocket.
Mark these words!
Meanwhile, the Gox verification queue keeps on growing. Now at 28,000+.
http://www.reddit.com/r/Bitcoin/comments/1ca5e4/mtgox_verification_times/c9eio88
http://www.reddit.com/r/Bitcoin/comments/1ca5e4/mtgox_verification_times/c9eio88
Betfair (sports bet exchange) can handle more transactions per second than the NYSE. They invented a technology called Flywheel which, apparently, allows them to do it with only 2 x $50,000 servers.
They wouldnt touch bitcoin with a bargepole, but if someone could hire their programmers, or license their technology things would be much improved.
http://www.hpts.ws/papers/2007/HPTS%20Workshop%20-%20Betfair%20-%20Flywheel.pdf
50,000 transactions per second.
They wouldnt touch bitcoin with a bargepole, but if someone could hire their programmers, or license their technology things would be much improved.
http://www.hpts.ws/papers/2007/HPTS%20Workshop%20-%20Betfair%20-%20Flywheel.pdf
50,000 transactions per second.
Speculations that this lag and ddos attacks are done so someone can sell off easy are unbased.Everyone can just hit a market sell and will be the first on the queue till his coins are all gone.And if he was doing it little by little he would have seen even more bids show up at every price level.Just like now after the lag is somewhat manageable.The problems are orchestrated to induce sells of many people consecutively who fear it might be late after 10min of lag.All this things are done because it is the only way to acquire coins from long term believers (even they have fears) and some miners because most of them don't trade and they might not show their coins ever on an exchange if the trend is up or at least there is no problems.If ten people want to amass 100k coins like the Winklevoss they will not see some of the coins ever show on the orderbook irrespective of the price so they need to give a reason to some people to show them - some kind of fear.It might not be even about what price the investor want to pay,some coins just won't show up if they are not stimulated.
Word.
There is no lack of people willing to buy bitcoins, so every talk of "trying hard to sell them" is entirely bullshit. I can buy any bitcoins that someone has to sell, at the actual OTC market bid price, not some manipulated blackbox magic. See hopea.fi for details, what the current buy is.
Stop blaming PHP/Mysql. I wrote a very simple PHP/Mysql Bid/Ask engine. It could execute ~35 orders in a second on a super nooby $300 server. Its pretty obvious they are doing something other than just a simple Bid/Ask engine to get this much lag.
I'm not blaming PHP, just the person who made it the core of a high volume, high user trading engine
At least it wasn't Java.
They are probably super scared of getting hacked again, so have developed an unorthodox way of executing trades.
Speculations that this lag and ddos attacks are done so someone can sell off easy are unbased.Everyone can just hit a market sell and will be the first on the queue till his coins are all gone.And if he was doing it little by little he would have seen even more bids show up at every price level.Just like now after the lag is somewhat manageable.The problems are orchestrated to induce sells of many people consecutively who fear it might be late after 10min of lag.All this things are done because it is the only way to acquire coins from long term believers (even they have fears) and some miners because most of them don't trade and they might not show their coins ever on an exchange if the trend is up or at least there is no problems.If ten people want to amass 100k coins like the Winklevoss they will not see some of the coins ever show on the orderbook irrespective of the price so they need to give a reason to some people to show them - some kind of fear.It might not be even about what price the investor want to pay,some coins just won't show up if they are not stimulated.
Stop blaming PHP/Mysql. I wrote a very simple PHP/Mysql Bid/Ask engine. It could execute ~35 orders in a second on a super nooby $300 server. Its pretty obvious they are doing something other than just a simple Bid/Ask engine to get this much lag.
I'm not blaming PHP, just the person who made it the core of a high volume, high user trading engine
At least it wasn't Java.
Stop blaming PHP/Mysql. I wrote a very simple PHP/Mysql Bid/Ask engine. It could execute ~35 orders in a second on a super nooby $300 server. Its pretty obvious they are doing something other than just a simple Bid/Ask engine to get this much lag.
Lots of shorting potential.
Gox down?
Gox down?
you really make me laugh ...
Their "trading engine" is just a PHP script that keeps a queue of orders, and executes them synchronously with each trade being it's own locking transaction to prevent errors. PHP isn't exactly known for its raw processing speed, nor is MySQL, by default. Of course there ARE high-volume sites using PHP, but they often use many tricks to make it run faster (like Facebook which uses PHP but recompiles parts of it to barebones C, lookup "HipHop" for more details). They've said that upon executing an order they have to check all matching orders for their validity. This means grabbing a ton of data from MySQL and iterating over it. This, combined with slow message queue (which as I said probably is just a PHP script, not a 0MQ or something else), gives us what we see now. And when people see lag, they sell even more, thus adding more to the already blocked queue.
Remember, the site was designed to trade Magic the Gathering cards, not trading thousands of Bitcoins per minute.
Remember, the site was designed to trade Magic the Gathering cards, not trading thousands of Bitcoins per minute.
MySQL is usually considered pretty speeds as DBs go. However, though I am usually a big SQL proponent, there are situations where it is not the best choice. My first thoughts about an exchange is that for something like this, you'd probably want a custom-built high-speed trading engine specifically designed and optimized for this kind of transaction. You could use SQL for accounting, record keeping and authentication etc but there are some optimizations you could do that just wouldn't translate to SQL very well, especially not SQL with PHP on top (and I'm by no means anti-PHP either).
it's back here too
Same, up for me.
Jump to: