Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: Tim MeagherHey,
When you say it's slower - what version have you upgraded from - i.e. where was it faster?
Also, do you know what sort of operations this affects?
Is it just when rerunning nodes, or when loading, or when executing any node (regardless of whether the node has already been run previously)?
I can't see anything which should have caused any noticeable change in performance from the 4.6.1 release to 5.0.
I know that from 4.5 to 4.6 there probably would have been some performance implications on graph navigation and the time taken for the signal to be sent to the server to execute nodes.
However, performance testing indicated that these weren't significantly large changes except on initiating the server connection.
From what I'm seeing, there shouldn't (I don't think) be any performance degradation from 4.6.1 to 5.0 looking at the code and the changes introduced.
I also haven't noticed this problem myself, so am curious.
The only thing I can see which could introduce slower performance is related to the way that BRE communicates to the server when it establishes a connection
Part of the reason for that is that BRE now respects the server's character set, so on connect, the protocol is a little more "chatty" and BRE queries the server for it's character set and sets the server code page based on the server's response.
However, once that connection is established I'm not seeing anything which would lead to slowdowns compared to the 4.6 branch.
Although I guess if you had the "Time to Connection Timeout" set to a non-zero value, and "Reconnect broken threads" checked in advanced preferences, then it might need to reconnect to the server regularly which could result in some slowdowns compared to 4.6.x...
Regards,
Tim.