Paul, I had all this spikes on NSCP and SEEK, they are correctable and this what brings you to not to be able to see them, if you load particular issue after it was corrected in your data base, you can't see the spike, you got to sit and watch something very active to increase probability of this "phenomenum" to appear. Don't forget also to put yourself in our shoes, I mean, create connection which simulate your client's end (myself, Al, ... anybody). Until you don't see problem you are not able to correct it. What I can tell you for sure it wasn't Al's connection, it was a spike transmitted by your equipment as well as most of stops of data flow are from your end. To be completely truthful, yesterday when NSCP reached incredible volume, your service, when it was working, was faster than not only Datek's real time quotes but also overspeeded, incredibly fast in normal conditions, Island applet.
Michael. |
