LoL....It's me again. Another bug is making itself shown
The Websocket is too sensitive and keeps disconnecting for short periods of time. I used to be able to keep it open all day, now I have to reconnect every 15 minutes or so... sometimes after just 5 minutes.
Topic: Real Time MtGox Order Book - page 3. (Read 26764 times)
MtGox needs to update their WebSockets 'stack'...
Cheers,
Kermee
I couldn't have said it better myself.
Not working with Firefox 6, for which Websocket is enabled by default.
MtGox needs to update their WebSockets 'stack'...
Cheers,
Kermee
Not working with Firefox 6, for which Websocket is enabled by default.
@Clark
send you donation for your great tool
send you donation for your great tool
I think MtGox is using an older version of the WebSocket protocol, which may or may not play a role in the incompatibility.
If the data came in over Secure WebSockets with a newer protocol, then I bet the compatibility would be more widespread.
If the data came in over Secure WebSockets with a newer protocol, then I bet the compatibility would be more widespread.
Anyone using Chrome 14 Beta having issues? Going from 12 to 14 seems to have broken WebSockets for me 
Cheers,
Kermee
Cheers,
Kermee
I'm having the same issue one two different PCs both running Chrome 14.0.835.94 Beta-m. I'm also having the issue with the canary channel build which is currently version 15.0.855.0 canary.
Currently the site works in Firefox 5 after changing the about:config setting network.websocket.override-security-block so that's what I'm using. The same setting does not work in FF6 so don't upgrade.
Heres a quick run down on my windows box.
Not working in...
Chrome 14.0.835.94 Beta-m
Chrome 15.0.855.0 canary
Firefox 6.0 (not even with network.websocket.override-security-block set to true)
Firefox Aurora 7.0a2 (2011-08-16)
Works in...
Firefox 5 (with network.websocket.override-security-block set to true)
Chrome 13.0.782.112 m
Ah. Good to know about FFV. Thanks.
I looked at the Dev logs... WebSockets was 'rehauled' in 14... So I'm not surprised it might of broken some things
Cheers,
Kermee
Anyone using Chrome 14 Beta having issues? Going from 12 to 14 seems to have broken WebSockets for me
Cheers,
Kermee
Cheers,
Kermee
I'm having the same issue one two different PCs both running Chrome 14.0.835.94 Beta-m. I'm also having the issue with the canary channel build which is currently version 15.0.855.0 canary.
Currently the site works in Firefox 5 after changing the about:config setting network.websocket.override-security-block so that's what I'm using. The same setting does not work in FF6 so don't upgrade.
Heres a quick run down on my windows box.
Not working in...
Chrome 14.0.835.94 Beta-m
Chrome 15.0.855.0 canary
Firefox 6.0 (not even with network.websocket.override-security-block set to true)
Firefox Aurora 7.0a2 (2011-08-16)
Works in...
Firefox 5 (with network.websocket.override-security-block set to true)
Chrome 13.0.782.112 m
Ok. All settings are now saved transparently in a cookie and loaded on startup.
This, of course, doesn't mean that it's too late to sponsor the default settings for newcomers.
And thanks toffoo for the great donation!
This, of course, doesn't mean that it's too late to sponsor the default settings for newcomers.
And thanks toffoo for the great donation!
I was just thinking about that as I clicked all of my preferred choices multiple times today. Stay tuned.
Edit: Of course you could also 'sponsor' the default configuration of the site
Edit: Of course you could also 'sponsor' the default configuration of the site
I would gladly store a cookie in my browser so that my preferences (10-line console, no visible calculator, no visible controls, group by 0.01) were remembered .
. 
Yes, I took those away, with the intent of adding an option, but the option never happened. Until now.
Truly awesome. Looks perfect now.
You sure know how to milk me, and I'm feeling less Bitcoin-poor today, so donation sent! to: 184FgjfDC2JB3EDWfPpYrv6uX77FzfNE5k
Thanks again Clark, please don't ever take this page down.
It looks like one of your very recent changes has altered the console display at the bottom of the screen.
I'd prefer to see them, or ideally have the option to display them.
I'd prefer to see them, or ideally have the option to display them.
Yes, I took those away, with the intent of adding an option, but the option never happened. Until now.
Enjoy.
Hi Clark,
It looks like one of your very recent changes has altered the console display at the bottom of the screen. I can't tell if this is a bug of some kind or if you changed this on purpose, but I no longer see the order ADD/REMOVE websocket messages scrolling by in the console, only trades and a few other info messages.
I'd prefer to see them, or ideally have the option to display them.
Thanks again for this great page.
It looks like one of your very recent changes has altered the console display at the bottom of the screen. I can't tell if this is a bug of some kind or if you changed this on purpose, but I no longer see the order ADD/REMOVE websocket messages scrolling by in the console, only trades and a few other info messages.
I'd prefer to see them, or ideally have the option to display them.
Thanks again for this great page.
Anyone using Chrome 14 Beta having issues? Going from 12 to 14 seems to have broken WebSockets for me
Cheers,
Kermee
Cheers,
Kermee
Site is working like a charm, thank you 
New Feature Announcement:
I have completed implementation of price grouping on the order book. It is available under the Controls section. You may group by 0.01, 0.05, 0.10, and 0.25 ($/BTC). This range may always be expanded depending on demand.
I think this feature will enable much greater awareness of the order book as a whole, similar to the graphical order books you see on other sites. With prices grouped, the order book is not a jumpy as before since row entries are not being added and removed that often.
Enjoy, and send bug reports (and donations)!
I have completed implementation of price grouping on the order book. It is available under the Controls section. You may group by 0.01, 0.05, 0.10, and 0.25 ($/BTC). This range may always be expanded depending on demand.
I think this feature will enable much greater awareness of the order book as a whole, similar to the graphical order books you see on other sites. With prices grouped, the order book is not a jumpy as before since row entries are not being added and removed that often.
Enjoy, and send bug reports (and donations)!
Ok, well I messed with the code a little bit, and I've eliminated a very inefficient jQuery call. Here is the updated table from my last post:
The new numbers are much more acceptable at the high row counts, especially considering that the book used to take almost a second (~800ms) to process a single message when displaying 500 rows.
GeniuSxBoy, thanks for pointing out how shamefully slow the update rate was and making me get in gear to produce more efficient code! The new code is now live.
Hint: for jQuery users, this is the power of the $.each() operator at work.
| Rows | Calc | No Calc |
| 50 | 10.1 | 9.3 |
| 100 | 19.1 | 17.2 |
| 250 | 47.1 | 45.7 |
| 500 | 73.6 | 72.1 |
The new numbers are much more acceptable at the high row counts, especially considering that the book used to take almost a second (~800ms) to process a single message when displaying 500 rows.
GeniuSxBoy, thanks for pointing out how shamefully slow the update rate was and making me get in gear to produce more efficient code! The new code is now live.
Hint: for jQuery users, this is the power of the $.each() operator at work.
Hmm, can you please remove the calculator and put it on a separate page that you can get to by a link on the page.
Ever since it was added, the website freezes waaaay more than it used to. I can't load the 500 or 1000 views anymore.
Ever since it was added, the website freezes waaaay more than it used to. I can't load the 500 or 1000 views anymore.
Here are some numbers that I gathered about the time (milliseconds) it takes to process a depth message. The calculator, when active, is set on selling 100 BTC and spending 100 USD
| Rows | Calc | No Calc |
| 50 | 39.7 | 37.7 |
| 100 | 82.1 | 81.7 |
| 250 | 350.3 | 346.7 |
| 500 | 832.2 | 778.1 |
As you can see, the numbers do not reflect a significant processing overhead for the calculator. However, I believe I could be more efficient when computing the sums all the way down the book.
You must keep in mind that MtGox sends messages out much faster than this page can display them. I believe the WebSocket gives on the order of 10-20 Hz data.
Here's a few questions:
How important is the sum column to you, especially at 500+ rows? Are you planning on releasing a 10000+ BTC buy any time soon (and will you let me know when you do)?
How exactly do you use the book when set at those high display counts? What are you looking at far away from the strike price?
I'd really like to make this thing more efficient, so any help will be appreciated. And I'll go look into making this code more efficient.
Hmm, can you please remove the calculator and put it on a separate page that you can get to by a link on the page.
Ever since it was added, the website freezes waaaay more than it used to. I can't load the 500 or 1000 views anymore.
Ever since it was added, the website freezes waaaay more than it used to. I can't load the 500 or 1000 views anymore.
Jump to: