v2.7.0.5
In the "NCrunch Distributed Processing Window", shouldn't (local) also have e.g. Status col updated? I find this window to be very useful when wanting to ensure all nodes are working, but to know if (local) is working I need to combine this with NCrunch Processing Queue.
General Feedback
Remote server: Shouldn't (local) also have Status/Server tasks updated?
Started by GreenMoose on 6,561 views
Remco NCrunch Developer
#5798
30 Apr 2014 11:40 UTC
At the moment, NCrunch doesn't do this, and the behaviour is by design. The reasoning behind the design has everything to do with implementation effort.
When the distributed processing UI (and its underlying message pipes) was first constructed, it wasn't intended to show information from the local machine. As such, it relies on backend wiring hooked directly into the internal monitoring within the grid nodes. None of this code was ever built into the client, so the only way to produce what would reasonably be expected is to 'dress up' the existing data already available in the processing queue, then try to find a way to display it similar to how this is done for the grid nodes.
I agree that it would be nice to support this, but the effort required is considerable. You're welcome to vote for it as a feature if you like.
When the distributed processing UI (and its underlying message pipes) was first constructed, it wasn't intended to show information from the local machine. As such, it relies on backend wiring hooked directly into the internal monitoring within the grid nodes. None of this code was ever built into the client, so the only way to produce what would reasonably be expected is to 'dress up' the existing data already available in the processing queue, then try to find a way to display it similar to how this is done for the grid nodes.
I agree that it would be nice to support this, but the effort required is considerable. You're welcome to vote for it as a feature if you like.
Edited 30 Apr 2014 11:40 UTC
Post a reply
Log in to reply.