6.0.2 installed just fine (even though it asked me to close firefox for some reason?)
- When I first rebooted and fired up QC, I got an error "local eSignal Data Mgr unable to connect...." that popped up once then disappeared. Haven't seen it since through multiple reboots and restarts.
- Performance is not perceptibly different for me from the last 6.x release. I built a very fast machine (E6850 3.0GHz core 2 duo) to run 6.x, so I don't notice any improvement in 6.0.2. If anything, loading multiple intraday charts when switching symbols may be a little slower in after hours. (see packet analysis below for a possibility)
- There still seems to be an issue of random intraday charts showing up blank when a new symbol is loaded. The chart stays blank as long as that symbol is cached. If you go away from that symbol for x period of time and come back, the chart will work properly. I did some packet sniffing when this occurred and data packets were flowing normally for that chart.... so I suspect the bug is in the display rather than the underlying data feed. My workaround is to either go away from that symbol for a few minutes and come back... or close and restart qcharts.
- There are still *lots* of TCP errors during the initial load of a workspace and particularly when a new symbol is loaded. I suspect this is the major reason for a delay in going from one symbol to the next in a quote sheet. I see a lot of "TCP previous segment lost" "TCP duplicate ACK" and "TCP out of order" indications during these transitions. Otherwise during a steady state when everything is quiet, the packets look pretty good. I have wireshark captures saved if anyone at eSignal happens to care. ????
- wireshark also sees some poorly formed TCP packets and other errors that aren't related to performance issues.
- also, why do you guys use already-assigned TCP ports (2190, 2198 and 2199 to name just a few, which are tivoconnect, onehome-remote, and onehome-help)? Stepping on already-registered ports could cause bizarre application issues or system crashes for some users.... IMO it's a pretty amateur mistake that would be expected from someone who was new to protocol development. See http://www.iana.org/assignments/port-numbers for reference. You should really register your common management ports with iana (and not step on ones already registered.)
- I haven't noticed any hangs or crashes in 6.0.2 *yet*... but I only saw them maybe once or twice a week with the last release.
- nit: option chain doesn't automatically update with each new symbol. i.e. say I'm looking at aci and click option chain... close the chain, load new symbol goog. Select chain again... it still shows ACI instead of goog. More of a hassle than anything.
- nit: it looks like with each release of 6.x, the option montage gets more and more restrictive on how many options are listed. Is there any way to open this up to be kitchen sink like 5.1 was. That was kind of nice to be able to see all options with a single click. Yeah, you can do it with the option chain, but it's more of a hassle.
- nit: quote sheet and option montage, it shure would be nice if format-auto size-width, etc was sticky so each time you loaded a new montage or quote sheet you didn't have to shrink it down.
That's all the free testing you'll get out of me today.
Hope this helps,
lugz
- When I first rebooted and fired up QC, I got an error "local eSignal Data Mgr unable to connect...." that popped up once then disappeared. Haven't seen it since through multiple reboots and restarts.
- Performance is not perceptibly different for me from the last 6.x release. I built a very fast machine (E6850 3.0GHz core 2 duo) to run 6.x, so I don't notice any improvement in 6.0.2. If anything, loading multiple intraday charts when switching symbols may be a little slower in after hours. (see packet analysis below for a possibility)
- There still seems to be an issue of random intraday charts showing up blank when a new symbol is loaded. The chart stays blank as long as that symbol is cached. If you go away from that symbol for x period of time and come back, the chart will work properly. I did some packet sniffing when this occurred and data packets were flowing normally for that chart.... so I suspect the bug is in the display rather than the underlying data feed. My workaround is to either go away from that symbol for a few minutes and come back... or close and restart qcharts.
- There are still *lots* of TCP errors during the initial load of a workspace and particularly when a new symbol is loaded. I suspect this is the major reason for a delay in going from one symbol to the next in a quote sheet. I see a lot of "TCP previous segment lost" "TCP duplicate ACK" and "TCP out of order" indications during these transitions. Otherwise during a steady state when everything is quiet, the packets look pretty good. I have wireshark captures saved if anyone at eSignal happens to care. ????
- wireshark also sees some poorly formed TCP packets and other errors that aren't related to performance issues.
- also, why do you guys use already-assigned TCP ports (2190, 2198 and 2199 to name just a few, which are tivoconnect, onehome-remote, and onehome-help)? Stepping on already-registered ports could cause bizarre application issues or system crashes for some users.... IMO it's a pretty amateur mistake that would be expected from someone who was new to protocol development. See http://www.iana.org/assignments/port-numbers for reference. You should really register your common management ports with iana (and not step on ones already registered.)
- I haven't noticed any hangs or crashes in 6.0.2 *yet*... but I only saw them maybe once or twice a week with the last release.
- nit: option chain doesn't automatically update with each new symbol. i.e. say I'm looking at aci and click option chain... close the chain, load new symbol goog. Select chain again... it still shows ACI instead of goog. More of a hassle than anything.
- nit: it looks like with each release of 6.x, the option montage gets more and more restrictive on how many options are listed. Is there any way to open this up to be kitchen sink like 5.1 was. That was kind of nice to be able to see all options with a single click. Yeah, you can do it with the option chain, but it's more of a hassle.
- nit: quote sheet and option montage, it shure would be nice if format-auto size-width, etc was sticky so each time you loaded a new montage or quote sheet you didn't have to shrink it down.
That's all the free testing you'll get out of me today.
Hope this helps,
lugz
Comment