Mt.Gox is a piece of shit

[BasementMiner!]

How about creating a order matching system not in fucking slow PHP?

[1714609562]

1714609562

[Bit_Happy]

Don't blame PHP, plenty of great sites use it.

[skilo]

Agreed, I just pulled all my remaining BTC out of Mt.gox, If they can't handle a large volume of sell orders then they have failed their intended purpose.

Fuck um.

[gweedo]

Don't blame PHP, plenty of great sites use it.

PHP is great, but for things like this a java application would handle the load better, and be able run orders a faster.

[BitcoinMint.US]

Your rant makes me want to put a "sold at $33 bought back at $41" meme in this thread.

[Raoul Duke]

Your rant makes me want to put a "sold at $33 bought back at $41" meme in this thread.

The amount of butthurt is imense, ain't it?

[Monster Tent]

Will coinlab use the mt gox api or setup their own trading site ?

[gweedo]

Don't blame PHP, plenty of great sites use it.

PHP is great, but for things like this a java application would handle the load better, and be able run orders a faster.

MMMMMM you're getting into very dangerous territory with that statement. First of all, php is pretty fast and lightweight compared to Java. Second, there are certain functions that are faster in PHP and certain functions that are faster in Java. But one particular key factor makes PHP the better choice: MySQL development teams and PHP development teams used to work pretty closely together to improve efficiency, I doubt very much that Java has the same speed when it comes to "talking" to MySQL then again, I'm not sure what back-end DB MTGox is using but if they are using PHP it's very easy to assume they are using MySQL as the backend, again, I can be wrong.

First off, just talking about java for the trading engine. Also if it was up to me, I wouldn't use mysql for trading engine store. I would use java because the logic would be faster for matching, also I would use a redis for the store, cause you have so many reads and writes that it better to have them in memory.

[gweedo]

Don't blame PHP, plenty of great sites use it.

PHP is great, but for things like this a java application would handle the load better, and be able run orders a faster.

MMMMMM you're getting into very dangerous territory with that statement. First of all, php is pretty fast and lightweight compared to Java. Second, there are certain functions that are faster in PHP and certain functions that are faster in Java. But one particular key factor makes PHP the better choice: MySQL development teams and PHP development teams used to work pretty closely together to improve efficiency, I doubt very much that Java has the same speed when it comes to "talking" to MySQL then again, I'm not sure what back-end DB MTGox is using but if they are using PHP it's very easy to assume they are using MySQL as the backend, again, I can be wrong.

First off, just talking about java for the trading engine. Also if it was up to me, I wouldn't use mysql for trading engine store. I would use java because the logic would be faster for matching, also I would use a redis for the store, cause you have so many reads and writes that it better to have them in memory.

You want to keep in memory an entire transactional system? Yeah, sure, that might work for your 100 lines advanced "Hello World" application, but for a production environment of the size of MTGox, with thousands or transactions per second, if not more, and the risk of losing data or a transaction if it's using only memory is too risk.. that's why there exist transactional databases

No only non-match trades would be in redis, and redis does write backups to the filesystem. Actually redis done right doesn't have the much more risk than mysql.

[Scrat Acorns]

No only non-match trades would be in redis, and redis does write backups to the filesystem. Actually redis done right doesn't have the much more risk than mysql.

You're a funny guy. You do realise that you need full ACID & transactional capability for a financial trading system right?

[gweedo]

No only non-match trades would be in redis, and redis does write backups to the filesystem. Actually redis done right doesn't have the much more risk than mysql.

You're a funny guy. You do realise that you need full ACID & transactional capability for a financial trading system right?

That is why you would use mysql to hold the data after a trading match was made. Actually did some research just know and actually an exchange on bitcointalk does use redis... So it can be done, https://bitcointalk.org/index.php?topic=60548.0

[gweedo]

Don't blame PHP, plenty of great sites use it.

PHP is great, but for things like this a java application would handle the load better, and be able run orders a faster.

MMMMMM you're getting into very dangerous territory with that statement. First of all, php is pretty fast and lightweight compared to Java. Second, there are certain functions that are faster in PHP and certain functions that are faster in Java. But one particular key factor makes PHP the better choice: MySQL development teams and PHP development teams used to work pretty closely together to improve efficiency, I doubt very much that Java has the same speed when it comes to "talking" to MySQL then again, I'm not sure what back-end DB MTGox is using but if they are using PHP it's very easy to assume they are using MySQL as the backend, again, I can be wrong.

First off, just talking about java for the trading engine. Also if it was up to me, I wouldn't use mysql for trading engine store. I would use java because the logic would be faster for matching, also I would use a redis for the store, cause you have so many reads and writes that it better to have them in memory.

You want to keep in memory an entire transactional system? Yeah, sure, that might work for your 100 lines advanced "Hello World" application, but for a production environment of the size of MTGox, with thousands or transactions per second, if not more, and the risk of losing data or a transaction if it's using only memory is too risk.. that's why there exist transactional databases

No only non-match trades would be in redis, and redis does write backups to the filesystem. Actually redis done right doesn't have the much more risk than mysql.

PHP can do the same and probably faster. I'd still use MySQL.
Java is inherently SLOWWWW look at Android phones hahahaha  j/k

PHP isn't faster than java in the logic of matching trades, plus PHP is event-based so you would have to have a cron job, where in java you can actually have the program do all the matching, with out delays.

[drawingthesun]

Compared to real trading platforms MtGox is rubbish. I really think they don't care because no one else in the community has made a better site yet. (Making a competitor is hard because you have to be legal and know your customer)

[tvbcof]

Zhou Tong could probably whip something out using redis in half a day (if Mt.Gox's actual matching engine does not already use it which I would find surprising.)  Someone else should probably do the security architecture though.