I'm going to see if CAT performs better on a windows server located in Tampa with a 1Gbps connection. I've also downgraded to 2.5 as it seems I was having less issues with it than 2.6. I'll let you know how it goes.
Bad idea the downgrade
![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif)
Algorithm from 2.5 to 2.6 is the same, but there's no problem with concurrent operation like "stop process"/"close ping orders" etc....
No, if the market froze, e.g. no log for hours in 2.5, I can stop the process without making the whole app frozen.
I am temporarily downgrading to 2.5 too.
This is the result of the change made in 2.6 to avoid "concurrency problem".
Concurrency is something like :
- CAT Process is running, and is working on 10 orders.
- You ask to cancel orders
- Orders are cancelled immediatedly
- CAT Process crash because he "think" to work on 10 orders.
In 2.6 is
- CAT Process is running, and is working on 10 orders.
- You ask to cancel orders
- CAT check if process is running, if yes, CAT add a requesto, if no, CAT Perform operation.
In Yes Case
- CAT Process perform and terminate all operations on the 10 orders.
- CAT Execute the cancel order request.
This process works on structures synchronized, it means that if Process A are Work on synchronized structure X, and process B wants to access X, B must wait for A to release.
And this is what happens :
- CAT Is Working and Cryptsy return error, CAT is Retrying (for a long time until timeout) : this is process A
- You ask to stop Process and CAT wants to know if there's an active process working : this is process B
B is waiting for A to stop, but A isn't stopping..........so CAT seems freeze.
I'm sure that when Cryptsy will return ok, all these problems will resolve